I actually think it's easier than what it seems.
Your cloud-init.service dist-upgrade and stops when it's running cloud-init
postinst. This is because the prerm and then postinst contaings default systemd
instructions:
prerm:
deb-systemd-invoke stop cloud-final.service cloud-config.target
cloud-config.service cloud-init-local.service cloud-init.service >/dev/null
-> stopping the service
postinst:
deb-systemd-invoke start cloud-final.service cloud-config.target
cloud-config.service cloud-init-local.service cloud-init.service >/dev/null ||
true
-> restarting the service
This will restart the service if already running (or start on install).
I think you don't really want this.
Here is a patch to ensure we don't have that behavior. However, you
still have the old prerm in the previous version of the package, so you
need an upload/an image + another upload to test it I guess?
** Patch added: "dont_autostart_cloud-init.debdiff"
https://bugs.launchpad.net/cloud-init/+bug/1438520/+attachment/4364891/+files/dont_autostart_cloud-init.debdiff
--
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
