cloud-final is never executed if upstart or any dependency is upgraded during initialization

cloud-config script used by lp:auto-package-testing

Please can you boot such a system with '--debug' and capture syslog / dmesg / console so we can try and work out what is happening here.

To reproduce outside of "cloud", you can basically follow the blog post that I've got at [1].

Using this user-data to make sure you can login:
#cloud-config-archive
- content: |
   #!/bin/sh
   echo "==== $(date -R): user-script run ===" | tee /run/user-script.log
- filename: myjob.conf
  content: |
   #upstart-job
   description "a test upstart job"
   start on stopped rc RUNLEVEL=[2345]
   console output
   task
   script
   echo "==== $(date -R): upstart job run ===" | tee /run/upstart-job.log
   end script
- content: |
   #cloud-config
   password: passw0rd
   chpasswd: { expire: False }
   ssh_pwauth: True

Then:
sudo apt-get install kvm cloud-utils genisoimage
wget http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd64-disk1.img -O disk.img.dist
qemu-img convert -O qcow2 disk.img.dist disk.img.orig

qemu-img create -f qcow2 -b disk.img.orig disk.img
cloud-localds my-seed.img my-user-data
kvm -net nic -net user,hostfwd=tcp::2222-:22 \
   -hda disk.img -hdb my-seed.img -m 512

Due to the fact that the bug blocks gettys from running, you'll have to ssh in.
Thats why i've done the host forwarding there.
You'll be able to log in with 'ubuntu' and 'passw0rd'. Remember that console output will be going to the serial device.

--
[1] http://ubuntu-smoser.blogspot.com/2013/02/using-ubuntu-cloud-images-without-cloud.html

I've added a simple reproduce for bug 1124384 under lxc . It seems likely to me at least that this bug and that one are related.

i see the issue even without an upstart upgrade.. my upgrade list is. note cloud-init is part of the list.

  apparmor apport apt apt-transport-https apt-utils base-files cloud-init curl
  gcc-4.7-base gir1.2-gudev-1.0 grub-common grub-legacy-ec2 grub-pc
  grub-pc-bin grub2-common kmod language-selector-common libapt-inst1.5
  libapt-pkg4.12 libc-bin libc6 libcurl3 libcurl3-gnutls libgcc1 libglib2.0-0
  libgudev-1.0-0 libisccc90 libkmod2 libpci3 libpython-stdlib libpython2.7
  libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib
  libpython3.3-minimal libpython3.3-stdlib libstdc++6 libudev1 login
  module-init-tools multiarch-support ntpdate passwd pciutils perl perl-base
  perl-modules python python-gi python-minimal python-pycurl
  python-twisted-bin python-twisted-core python2.7 python2.7-minimal python3
  python3-apport python3-distupgrade python3-gi python3-minimal
  python3-problem-report python3-update-manager python3.3 python3.3-minimal
  rsyslog tar ubuntu-minimal ubuntu-release-upgrader-core ubuntu-standard udev
  update-manager-core update-notifier-common

Kapil,
 your upgrade list includes 'glibc' which is a library dependency of upstart. Because of that, a restart of upstart is necessary.
 (/var/lib/dpkg/info/libc6:amd64.postinst invokes 'telinit u').

Just for reference 'grep -r "telinit u" /var/lib/dpkg/info' on my system shows:
  libjson0
 libnih1
 libnih-dbus1
 libc6
 libselinux1
 libdbus-1-3
 upstart

With juju 1.24 this bug appears to be hit on state servers started with 'juju ensure-availability' during cloud-init upgrade, unless enable-os-refresh-update and enable-os-upgrade are set to false.