Talking with didrocks, there is no clear way to stop the installed prerm from running. We could definitely come up with some solution for addressing this problem, but have decided its easiest and acceptable to just upload and accept that images (not instances) that have the older version of cloud-init inside them will fail.
This change will essentially put us back to the behavior we had with upstart, which worked acceptbly for 4 years. The end result is: * we'll release new dailies and new released images with this version inside. * As soon as there are daily images and released images available with this fixed version of cloud-init * users who run older images (beta-2) will still fail. * future upgrades of cloud-init will not suffer this issue. Other things we could have done to address this: * cloud-init ignore sigterm and finish what it was doing. this would (if it was too slow) still get killed by systemd eventually, so not really a solution. * cloud-init not upgrade itself (apt-pin itself, then remove the pin). * cloud-init final could realize thta cloud-config hadn't finished and cloud-config's modules before running its own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438520 Title: cloud-init on vivid upgrade causes sigterm, which aborts 'runcmd' execution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1438520/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
