[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Stephen, can you please tell us what the affected kernel versions are? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Raising to critical as this breaks Azure users. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
This commit is in the upstream kernel tree and has been backported to every Ubuntu kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Package changed: linux (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
OK, I'm shifting this back to linux, because I think that the commit that was backported is fixing a problem in a commit that _wasn't_ backported, therefore causing the issue. Here are the details: In 95be58df7 [0], support for SMBIOS 3 was added, which introduces a third version field (i.e. 3.2.1 vs. 2.9); as a result, dmi_ver is converted from a u16 and a u32, and when it's read in, it's left-shifted 8 bits. (i.e. version 2.6 goes from 0x0206 to 0x020600). The endian-ness checks are updated to match the shifted number (i.e. if SMBIOS version >= 0x020600, little-endian, otherwise big-endian). This patch has NOT been backported to trusty. In ff4319dc7 [1], it was identified that this left-shifting happened in the wrong place, and so it was moved to happen in a different place. Simple enough. However, this patch HAS been backported to trusty, despite the fact it is fixing behaviour that wasn't backported. Crucially, though, the commit containing the backport [2] introduced the left-shifting _without_ changing the endian-ness checks. This means that the trusty kernel _always_ detects the SMBIOS version as being greater than 2.6, which means on older versions of SMBIOS (like the one in use on Azure), it returns the version with incorrect endian-ness. [0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=95be58df74a5b21e5a78e45fddb2fd59112524c5 [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=ff4319dc7cd58c92b389960e375038335d157a60 [2] http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e ** Package changed: cloud-init (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Thanks to Steve Z for pointing out that it works in wily; that's what sent me down this path. It works in wily because wily _does_ have 95be58df7. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
So in addition to a kernel fix, we will first need to release a cloud- init that will handle the endian-ness of instance IDs changing underneath it. This is because the kernel is already out in the wild, so we will have some instances that have booted with the new UUID and the kernel fix will also trigger the behaviour seen in this bug. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: cloud-init (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux (Ubuntu) Assignee: Dan Watkins (daniel-thewatkins) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in cloud-init source package in Trusty: New Status in linux source package in Trusty: New Status in cloud-init source package in Vivid: New Status in linux source package in Vivid: New 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Description changed: 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 corrects the endianness - for some SMBIOS fields, but also has the effect causing cloud-init to - think that the system-uuid has changed: + 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 - The impact is that cloud-init attempts to reprovision the VM, often - causing the customer to lose access to their VM. + 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: + + 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. + + [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. ** Description changed: 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: + 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. + 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in cloud-init source package in Trusty: New Status in linux source package in Trusty: Fix Committed Status in cloud-init source package in Vivid: New Status in linux source package in Vivid: Fix Committed 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in cloud-init source package in Trusty: New Status in linux source package in Trusty: Fix Committed Status in cloud-init source package in Vivid: New Status in linux source package in Vivid: New 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 corrects the endianness for some SMBIOS fields, but also 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 The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
It seems the Utopic kernel is impacted as well, I tested 3.16.0-62-generic released on 2/27. I thought that kernel was EOL. Can we revert the fix here as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in cloud-init source package in Trusty: New Status in linux source package in Trusty: Fix Committed Status in cloud-init source package in Vivid: New Status in linux source package in Vivid: Fix Committed 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Luis Henriques (henrix) ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in cloud-init source package in Trusty: New Status in linux source package in Trusty: Fix Committed Status in cloud-init source package in Vivid: New Status in linux source package in Vivid: Fix Committed 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-utopic (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-lts-utopic (Ubuntu Trusty) Assignee: (unassigned) => Luis Henriques (henrix) -- 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: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: New Status in cloud-init source package in Trusty: New Status in linux 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: New Status in linux source package in Vivid: Fix Committed 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided => Critical -- 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: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: New Status in cloud-init source package in Trusty: New Status in linux 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: New Status in linux source package in Vivid: Fix Committed 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Also affects: linux-keystone (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-keystone (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-keystone (Ubuntu) Status: New => Invalid ** Changed in: linux-keystone (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-keystone (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: linux-keystone (Ubuntu Trusty) Assignee: (unassigned) => Luis Henriques (henrix) -- 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: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress 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: New 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: New 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. 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Description changed: 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. -- 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: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress 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: New 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: New 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Attached is a debdiff for trusty (the only affected version). ** Patch added: "lp1551419.debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/cloud-init/+bug/1551419/+attachment/4587505/+files/lp1551419.debdiff -- 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: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: In Progress 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: New 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: New 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
[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Changed in: cloud-init (Ubuntu Trusty) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Trusty) Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) ** Changed in: cloud-init (Ubuntu) Status: In Progress => Invalid ** Changed in: cloud-init (Ubuntu) Assignee: Dan Watkins (daniel-thewatkins) => (unassigned) ** Changed in: cloud-init (Ubuntu Vivid) Status: New => Invalid ** Summary changed: - Fix UUID endianness patch breaks cloud-init on Azure + [SRU] Fix UUID endianness patch breaks cloud-init on Azure ** Summary changed: - [SRU] Fix UUID endianness patch breaks cloud-init on Azure + [SRU] Handle changing UUID endian-ness on Azure in cloud-init -- 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: In Progress 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
