| 2016-02-29 20:49:24 |
Stephen A. Zarkos |
bug |
|
|
added bug |
| 2016-02-29 21:00:09 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2016-02-29 21:07:33 |
Stephen A. Zarkos |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2016-02-29 21:16:27 |
Ben Howard |
linux (Ubuntu): importance |
Undecided |
Critical |
|
| 2016-02-29 23:35:26 |
Ben Howard |
affects |
linux (Ubuntu) |
cloud-init (Ubuntu) |
|
| 2016-02-29 23:57:58 |
Ben Howard |
branch linked |
|
lp:~utlemming/cloud-init/lp1551419 |
|
| 2016-03-01 00:08:51 |
Ben Howard |
branch unlinked |
lp:~utlemming/cloud-init/lp1551419 |
|
|
| 2016-03-01 15:06:13 |
Joseph Salisbury |
tags |
|
kernel-da-key |
|
| 2016-03-02 03:58:26 |
Patricia Gaughen |
cloud-init (Ubuntu): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
| 2016-03-02 11:14:38 |
Dan Watkins |
affects |
cloud-init (Ubuntu) |
linux (Ubuntu) |
|
| 2016-03-02 12:42:05 |
Dan Watkins |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2016-03-02 12:42:10 |
Dan Watkins |
cloud-init (Ubuntu): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
| 2016-03-02 13:48:26 |
Dan Watkins |
cloud-init (Ubuntu): status |
New |
In Progress |
|
| 2016-03-02 14:00:43 |
Patricia Gaughen |
linux (Ubuntu): assignee |
Dan Watkins (daniel-thewatkins) |
|
|
| 2016-03-02 16:39:10 |
Luis Henriques |
nominated for series |
|
Ubuntu Vivid |
|
| 2016-03-02 16:39:10 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Vivid) |
|
| 2016-03-02 16:39:10 |
Luis Henriques |
bug task added |
|
cloud-init (Ubuntu Vivid) |
|
| 2016-03-02 16:39:10 |
Luis Henriques |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-03-02 16:39:10 |
Luis Henriques |
bug task added |
|
linux (Ubuntu Trusty) |
|
| 2016-03-02 16:39:10 |
Luis Henriques |
bug task added |
|
cloud-init (Ubuntu Trusty) |
|
| 2016-03-02 17:14:36 |
Luis Henriques |
linux (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2016-03-02 17:28:31 |
Luis Henriques |
linux (Ubuntu Vivid): status |
New |
Fix Committed |
|
| 2016-03-02 17:30:26 |
Dan Watkins |
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. |
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:
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. |
|
| 2016-03-02 17:33:23 |
Dan Watkins |
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:
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. |
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. |
|
| 2016-03-03 10:17:34 |
Andy Whitcroft |
linux (Ubuntu Trusty): importance |
Undecided |
Critical |
|
| 2016-03-03 10:17:36 |
Andy Whitcroft |
linux (Ubuntu Vivid): importance |
Undecided |
Critical |
|
| 2016-03-03 10:17:51 |
Andy Whitcroft |
linux (Ubuntu Trusty): assignee |
|
Luis Henriques (henrix) |
|
| 2016-03-03 10:18:04 |
Andy Whitcroft |
linux (Ubuntu Vivid): assignee |
|
Luis Henriques (henrix) |
|
| 2016-03-03 10:47:43 |
Luis Henriques |
bug task added |
|
linux-lts-utopic (Ubuntu) |
|
| 2016-03-03 10:47:55 |
Luis Henriques |
linux-lts-utopic (Ubuntu Vivid): status |
New |
Invalid |
|
| 2016-03-03 10:48:02 |
Luis Henriques |
linux-lts-utopic (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2016-03-03 10:48:05 |
Luis Henriques |
linux-lts-utopic (Ubuntu Trusty): assignee |
|
Luis Henriques (henrix) |
|
| 2016-03-03 11:54:39 |
Andy Whitcroft |
linux-lts-utopic (Ubuntu Trusty): importance |
Undecided |
Critical |
|
| 2016-03-03 12:28:32 |
Andy Whitcroft |
bug task added |
|
linux-keystone (Ubuntu) |
|
| 2016-03-03 12:28:47 |
Andy Whitcroft |
linux-keystone (Ubuntu Vivid): status |
New |
Invalid |
|
| 2016-03-03 12:29:03 |
Andy Whitcroft |
linux-keystone (Ubuntu): status |
New |
Invalid |
|
| 2016-03-03 12:29:23 |
Andy Whitcroft |
linux-keystone (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2016-03-03 12:29:44 |
Andy Whitcroft |
linux-keystone (Ubuntu Trusty): importance |
Undecided |
Critical |
|
| 2016-03-03 12:29:44 |
Andy Whitcroft |
linux-keystone (Ubuntu Trusty): assignee |
|
Luis Henriques (henrix) |
|
| 2016-03-03 12:44:04 |
Dan Watkins |
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. |
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. |
|
| 2016-03-03 15:10:50 |
Dan Watkins |
attachment added |
|
lp1551419.debdiff https://bugs.launchpad.net/ubuntu/vivid/+source/cloud-init/+bug/1551419/+attachment/4587505/+files/lp1551419.debdiff |
|
| 2016-03-03 15:57:11 |
Dan Watkins |
cloud-init (Ubuntu Trusty): status |
New |
In Progress |
|
| 2016-03-03 15:57:20 |
Dan Watkins |
cloud-init (Ubuntu Trusty): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
| 2016-03-03 15:57:29 |
Dan Watkins |
cloud-init (Ubuntu): status |
In Progress |
Invalid |
|
| 2016-03-03 15:57:37 |
Dan Watkins |
cloud-init (Ubuntu): assignee |
Dan Watkins (daniel-thewatkins) |
|
|
| 2016-03-03 15:57:46 |
Dan Watkins |
cloud-init (Ubuntu Vivid): status |
New |
Invalid |
|
| 2016-03-03 16:00:15 |
Dan Watkins |
summary |
Fix UUID endianness patch breaks cloud-init on Azure |
[SRU] Fix UUID endianness patch breaks cloud-init on Azure |
|
| 2016-03-03 16:01:55 |
Dan Watkins |
summary |
[SRU] Fix UUID endianness patch breaks cloud-init on Azure |
[SRU] Handle changing UUID endian-ness on Azure in cloud-init |
|
| 2016-03-03 16:02:21 |
Dan Watkins |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-03-03 23:25:29 |
Adam Conrad |
cloud-init (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2016-03-03 23:25:36 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2016-03-03 23:25:41 |
Adam Conrad |
tags |
kernel-da-key |
kernel-da-key verification-needed |
|
| 2016-03-04 17:29:35 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/linux-lts-vivid |
|
| 2016-03-08 16:39:20 |
Dan Watkins |
tags |
kernel-da-key verification-needed |
kernel-da-key verification-done |
|
| 2016-03-08 18:46:29 |
Launchpad Janitor |
cloud-init (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-03-08 18:46:33 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-03-08 20:21:17 |
Ubuntu Foundations Team Bug Bot |
tags |
kernel-da-key verification-done |
kernel-da-key patch verification-done |
|
| 2016-03-08 20:21:17 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Joseph Salisbury |
| 2016-03-09 21:16:47 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2016-03-14 03:06:48 |
Mathew Hodson |
bug task deleted |
linux-lts-utopic (Ubuntu) |
|
|
| 2016-03-14 03:06:56 |
Mathew Hodson |
bug task deleted |
linux-lts-utopic (Ubuntu Vivid) |
|
|
| 2016-03-14 14:01:42 |
Launchpad Janitor |
linux (Ubuntu Vivid): status |
Fix Committed |
Fix Released |
|
| 2016-03-14 14:01:42 |
Launchpad Janitor |
cve linked |
|
2016-2384 |
|
| 2016-03-14 14:09:00 |
Launchpad Janitor |
linux (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-03-14 14:11:23 |
Launchpad Janitor |
linux-lts-utopic (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-03-15 10:16:38 |
Launchpad Janitor |
linux-keystone (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-05-31 13:25:27 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty/cloud-init |
|
