yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

hi. this is really a dupe of bug 972077.
Apt in 16.04 should not have any non-transient errors.
Thus, marking this fix-released.  In order to get a re-try back to trusty, we could potentially SRU a fix, but that is arguably just hiding underlying problems.  That said, since those underlying problems are now fixed in 16.04, i'm more apt to bother hiding them in older releases.


** Changed in: cloud-init
   Importance: Undecided => High

** Changed in: cloud-init
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1594967

Title:
  cloud-init lack of retry causes apt-get failures to be fatal

Status in cloud-init:
  Fix Released

Bug description:
  We use cloudinit to do apt-gets to install software. apt-gets fail
  ~20% of the time and it seems to be increasing.

      W: An error occurred during the signature verification. The repository is not updated and the previous index files 
      will be used. GPG error: http://us-central1.gce.archive.ubuntu.com trusty-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21
      F32

  Manually doing the command below a few times solves the problem, but
  cloudinit doesn't have any retry logic around this so having stable
  apt repositories is very important to have a repeatable process. What
  do you recommend if the repos won't be stable? I would think a simple
  retry in cloud-init (either configurable or 5x or something sane)
  would be very helpful.

      apt-key adv --keyserver keyserver.ubuntu.com --recv-keys XXXXXXX XXXXXXXX
      apt-get update

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1594967/+subscriptions