yahoo-eng-team team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

The apt-daily-upgrade service already declares itself to be 'After=apt-
daily.service'.  So there should be strict sequencing here of cloud-
final.service -> apt-daily.service -> apt-daily-upgrade.service.  If
that's not happening, this warrants analysis to understand why so that
it can be fixed in the apt package directly rather than adding more
relationships to the cloud-init unit.

** Changed in: cloud-init
       Status: New => Incomplete

** Also affects: apt (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: apt (Ubuntu)
       Status: New => Incomplete

** Changed in: apt (Ubuntu)
   Importance: Undecided => High

-- 
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/1711428

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

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