On Thu, Aug 17, 2017 at 07:59:00PM -0000, Jim Browne wrote: > However, is juliank's note about the implementation of After= a concern > w.r.t. how LP#1693361 was resovled?
I don't think so. He's correct that the ordering doesn't guarantee that we don't hit a conflict if the units wrap around and collide in the opposite direction. But I believe that locking code is part of the fix that landed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
