Hello Stephen, or anyone else affected, Accepted cloud-init into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.5-0ubuntu1.17 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: [SRU] Handle changing UUID endian-ness on Azure in cloud-init Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-keystone package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: New Status in cloud-init source package in Trusty: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-keystone source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in cloud-init source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-keystone source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: On Azure, cloud-init relies on the system-uuid as based by SMBIOS a unique ID for a cloud instance. If this ID ever changes, then cloud- init will attempt to reprovision the VM. This recent kernel patch in the Ubuntu kernel incorrectly modifies the endianness for some SMBIOS fields, which has the effect causing cloud- init to think that the system-uuid has changed: http://kernel.ubuntu.com/git/ubuntu/ubuntu- trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e cloud-init needs to consider both the reported UUID and the "first three fields endian-reversed" UUID as the same, so that users shifting between unaffected kernels and affected kernels, or affected kernels and fixed kernels do not see their instances reprovisioned. [Impact] The impact is that cloud-init attempts to reprovision VMs when they reboot to use the new kernel, often causing the customer to lose access to their VM. Once the kernel is fixed, rebooting from an affected kernel to the new kernel will have the same effect. [Test Case] Failure: 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB) 2) Upgrade the kernel and reboot. 3) SSH to the instance; you will observe that you are prompted to change SSH host keys because cloud-init has run again. Success (upgrade from not broken->broken): 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB) 2) Install the new version of cloud-init. 3) Upgrade the kernel and reboot. 4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again. 5) Make a note of the instance ID in use (i.e. the target of /var/lib/cloud/instance 6) Reboot again. 7) Observe that the instance ID has not changed. Success (upgrade from broken->fixed): 1) Boot an Azure instance using an image with a broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB) 2) Install the new version of cloud-init. 3) Upgrade to the fixed kernel (once it is available) and reboot. 4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again. Success (upgrade from not broken->fixed): 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB) 2) Install the new version of cloud-init. 3) Upgrade to the fixed kernel (once it is available) and reboot. 4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again. [Regression Potential] The change is limited to the Azure data source. It affects how instance IDs are determined, but the change does so in a limited way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
