Comment 0 for bug 1049146

I spawned a lucid AWS instance and used some cloud-init config to perform some tasks for me.

All is good.

Then, as part of the task I was performing, I upgraded that lucid instance to precise using do-release-upgrade. It failed, but unrelated to cloud-init (a postinst from a package failed).

I then rebooted the instance. When it came back up, the cloud-init config I supplied the first time was run again, as if this was the first time the instance booted.

smoser had access to before and after reboot, and asked to add this to the bug:
# for x in /var/lib/cloud/instance/sem/*; do [ -f var-lib-cloud/instance/sem/${x##*/} ] || echo ${x##*/}; done
config-byobu
config-ca-certs
config-chef
config-grub-dpkg
config-keys-to-console
config-landscape
config-mcollective
config-phone-home
config-rightscale_userdata
config-rsyslog
config-salt-minion
config-scripts-per-instance
config-scripts-user
config-set-passwords
config-ssh-import-id
config-timezone