[Bug 1438520] Re: cloud-init on vivid upgrade causes sigterm, which aborts 'runcmd' execution

[Scott Moser]

Above was long winded. A summary.
 * cloud-init has 4 services and 1 target . see those at [1]
 * cloud-config.service invoked 'apt-get dist-upgrade', and received a SIGTERM
 * cloud-config.service *would* have subsequently written a file into /var/lib/cloud/instance/scripts/
 * cloud-final.service did run.  Had it seen the script written it would have run it, but nothing was there to run.

So I think what happened is that the upgrade somehow sent SIGTERM to
cloud-config.service which made it stop prematurely. I dont think that
happened with upstart.

Any ideas here?
--
[1] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/systemd/


** Changed in: cloud-init
   Importance: Undecided => High

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

** Tags added: cloud-images systemd-boot

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in 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