Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2629

apt-get: Failed to fetch http://pkg.jenkins-ci.org

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      Fixed by 22:00 UTC Jun 4, 2020

      Description

      I'm seeing an issue similar to https://issues.jenkins-ci.org/browse/INFRA-557

      $ sudo apt dist-upgrade -y
      {{ Reading package lists... Done}}
      {{ Building dependency tree }}
      {{ Reading state information... Done}}
      {{ Calculating upgrade... Done}}
      {{ The following packages will be upgraded:}}
      {{ jenkins}}
      {{ 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.}}
      {{ Need to get 66.0 MB of archives.}}
      {{ After this operation, 430 kB of additional disk space will be used.}}
      {{ Err:1 https://pkg.jenkins.io/debian binary/ jenkins 2.239}}
      {{ 404 The specified blob does not exist.}}
      {{ E: Failed to fetch https://pkg.jenkins.io/debian/binary/jenkins_2.239_all.deb 404 The specified blob does not exist.}}E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

      I assume something in a release pipeline has failed.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Executed packaging again without the Windows stage. Delivered packages to the Debian and CentOS repositories. Confirmed installation works on Debian testing

          Show
          markewaite Mark Waite added a comment - Executed packaging again without the Windows stage. Delivered packages to the Debian and CentOS repositories. Confirmed installation works on Debian testing
          Hide
          lyda Kevin Lyda added a comment -

          This is broken again.

          Is it possible to complete the Debian package generation and deployment before doing the Windows part? This tends to mess up automated system management.

          Show
          lyda Kevin Lyda added a comment - This is broken again. Is it possible to complete the Debian package generation and deployment before doing the Windows part? This tends to mess up automated system management.
          Hide
          slide_o_mix Alex Earl added a comment -

          We're working on fixing the Windows portion. The process is Build -> Package, so if part of the Build stage fails on any platform, it can cause issues. We are working on it.

          Show
          slide_o_mix Alex Earl added a comment - We're working on fixing the Windows portion. The process is Build -> Package, so if part of the Build stage fails on any platform, it can cause issues. We are working on it.
          Hide
          olblak Olivier Vernin added a comment -

          I didn't have the time to seriously looking at it, but this problem seems weird to me, all packages are build and published into a staging directory in parallel and we explicitly specify 'faiFast' set to false link so we complete all parallel tasks before failing. Then there is a second script that uploads packages to various location and then promote staging directory into production link.
          This latest script is both called from the packaging job (last step) and from pkg.jenkins.io on a regular basis trigger by a cronjob, so at the moment calling that script from the packaging job is more to be sure that it's called right after packaging something than really promoting artifacts. there is a Jira ticket to solve the later issue INFRA-2608

          Show
          olblak Olivier Vernin added a comment - I didn't have the time to seriously looking at it, but this problem seems weird to me, all packages are build and published into a staging directory in parallel and we explicitly specify 'faiFast' set to false link so we complete all parallel tasks before failing. Then there is a second script that uploads packages to various location and then promote staging directory into production link . This latest script is both called from the packaging job (last step) and from pkg.jenkins.io on a regular basis trigger by a cronjob, so at the moment calling that script from the packaging job is more to be sure that it's called right after packaging something than really promoting artifacts. there is a Jira ticket to solve the later issue INFRA-2608
          Hide
          olblak Olivier Vernin added a comment -

          It seems that the needed package hasn't been published yet on Azure which is done in this line and happened before promoting from staging to production directories

          Show
          olblak Olivier Vernin added a comment - It seems that the needed package hasn't been published yet on Azure which is done in this line and happened before promoting from staging to production directories
          Hide
          markewaite Mark Waite added a comment -

          Confirmed working also with 2.243 July 2, 2020

          Show
          markewaite Mark Waite added a comment - Confirmed working also with 2.243 July 2, 2020

            People

            Assignee:
            markewaite Mark Waite
            Reporter:
            lyda Kevin Lyda
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: