On Thu, Aug 17, 2017 at 07:20:20PM -0000, Jim Browne wrote: > Hmmm. I confirm what you see.
> I think this problem is arising because we have Packer run (due to > LP#1693361): > systemctl disable apt-daily.service > systemctl disable apt-daily.timer > when building the AMI. > I guess if apt-daily.service is disabled the Before is not transitive > from cloud-init to apt-daily-upgrade via apt-daily? Not seeing anything > definitive in the docs after a quick glance. Correct. Before/After only establishes ordering between enabled services and is ignored for services that are not enabled. Fixing this to enforce that apt-daily.service and apt-daily-upgrade.service are both always enabled/disabled together would be done by adding 'Requires=apt-daily.service' to apt-daily-upgrade.service. But I think that is too strict, because one may legitimately choose to disable only one of the two services for some reason. So I think this is something that you will want to fix in your image mastering scripts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711428 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily- upgrade.service execution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
