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

[Scott Moser]

For doc and future reference, here is what I did to test that we'll be
fine in the future.

 - launch an instance of vivid with unpatched cloud-init (0.7.7~bzr1088-0ubuntu1) and no user-data.
 - dpkg -i install a version with this fix in place (0ubuntu2~sm0)
 - upload to ppa an even newer version (0ubuntu2~sm1)
 - write the following into /etc/cloud/cloud.cfg.d/99-smoser.cfg
   |#cloud-config
   |package_upgrade: true
   |apt_sources:
   | - source: "ppa:smoser/ppa"
   |runcmd:
   | - [sh, '-c', 'echo ====== hi world ======= 2>&1 | tee /run/greeting.log']
 - rm -Rf /var/lib/cloud/ /var/log/cloud-init*


So at this point, the system now has a patched cloud-init installed, and its marker files signalling "first instance boot" have been removed.  On reboot, it will add the ppa and attempt to upgrade, which will see the new cloud-init.

So to verify, we just ssh back in after reboot and check to make sure
/run/greeting.log exists. It did.

Note, we could have also just added the ppa before reboot with 'add-apt-
repository', which might have removed some moving parts.

-- 
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