| 2017-04-26 20:25:47 |
Stephen A. Zarkos |
bug |
|
|
added bug |
| 2017-04-26 20:27:27 |
Stephen A. Zarkos |
description |
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919. |
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
*This was tested on Ubuntu 16.04 - but may affect other releases.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919. |
|
| 2017-04-26 20:27:55 |
Stephen A. Zarkos |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4868359/+files/cloud-init.log |
|
| 2017-04-26 20:28:37 |
Stephen A. Zarkos |
attachment added |
|
cloud-init-output.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4868360/+files/cloud-init-output.log |
|
| 2017-04-27 22:19:46 |
David Britton |
cloud-init (Ubuntu): assignee |
|
Scott Moser (smoser) |
|
| 2017-04-27 22:41:36 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2017-04-28 13:20:00 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2017-04-28 13:20:04 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-04-28 13:20:08 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2017-04-28 13:20:14 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2017-04-28 13:20:17 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2017-04-28 18:36:27 |
Scott Moser |
cloud-init (Ubuntu): importance |
Medium |
High |
|
| 2017-04-28 18:36:39 |
Scott Moser |
cloud-init (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-04-29 00:56:58 |
Scott Moser |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/323420 |
|
| 2017-05-12 15:26:39 |
Scott Moser |
cloud-init: status |
Confirmed |
In Progress |
|
| 2017-05-16 21:31:30 |
Stephen A. Zarkos |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4877814/+files/cloud-init.log |
|
| 2017-05-17 14:21:36 |
Scott Moser |
description |
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
*This was tested on Ubuntu 16.04 - but may affect other releases.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919. |
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
*This was tested on Ubuntu 16.04 - but may affect other releases.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919.
Related bugs:
* bug 1691489: fstab entries written by cloud-config may not be mounted |
|
| 2017-05-17 16:05:49 |
Scott Moser |
cloud-init: status |
In Progress |
Fix Committed |
|
| 2017-05-17 16:05:53 |
Scott Moser |
cloud-init: assignee |
|
Scott Moser (smoser) |
|
| 2017-05-17 20:37:58 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-05-17 20:37:58 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2017-05-17 20:37:58 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-05-17 20:37:58 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2017-05-17 20:37:58 |
Scott Moser |
nominated for series |
|
Ubuntu Artful |
|
| 2017-05-17 20:37:58 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Artful) |
|
| 2017-05-17 20:37:58 |
Scott Moser |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-05-17 20:37:58 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Zesty) |
|
| 2017-05-17 20:38:07 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-05-17 20:38:09 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-05-17 20:38:12 |
Scott Moser |
cloud-init (Ubuntu Zesty): status |
New |
Confirmed |
|
| 2017-05-17 20:38:15 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-05-17 20:38:17 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2017-05-17 20:38:20 |
Scott Moser |
cloud-init (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-05-18 00:25:58 |
Stephen A. Zarkos |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4878669/+files/cloud-init.log |
|
| 2017-05-23 21:31:01 |
Launchpad Janitor |
cloud-init (Ubuntu Artful): status |
In Progress |
Fix Released |
|
| 2017-05-26 20:50:54 |
Scott Moser |
description |
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
*This was tested on Ubuntu 16.04 - but may affect other releases.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919.
Related bugs:
* bug 1691489: fstab entries written by cloud-config may not be mounted |
=== Begin SRU Template ===
[Impact]
On Azure, cloud-init handles re-formatting the ephemeral disk.
The contents of the ephemeral disk for a system will be replaced with
a stock ephemeral disk in the following scenarios:
a.) first boot
b.) after a resize.
c.) after a VM has been migrated from one host to another.
That ephemeral disk is either
1. mbr partitioned with 1 ntfs partition
2. gpt partitioned with 2 partitions, a msft reserved partition and a
ntfs partition. This scenario is newer, and only occurs on
larger instance types that have large ephemeral disks.
cloud-init previously did not handle '2' above.
[Test Case]
Generically this is re-creatable by:
1.) launch an instance on Azure
2.) resize it to a L32 or G5 size
3.) check to see that the ephemeral disk (/dev/disk/cloud/azure_resource)
has been formatted to ext4.
It is more easily recreated for testing and verification by:
1. launch instance on azure
2. re-partition the ephemeral disk to look like a "clean" disk above
3. remove old logs, reboot
$ dir=logs-$(date +"%Y%m%d-%H%M%S");
$ mkdir -p $dir; mv /var/log/cloud-init* $dir
4. ssh back in, expect that this the disk has an ext4 filesystem on it.
And that it is mounted on /mnt.
$ grep reformattable= /var/log/cloud-init.log
2017-05-12 15:14:57,125 - DataSourceAzure.py[DEBUG]: reformattable=False: partition 1 (/dev/sdb1) on device /dev/disk/cloud/azure_resource was not ntfs formatted
Or, if it was formatted, you'll see something like:
2017-05-12 15:17:47,021 - DataSourceAzure.py[DEBUG]: reformattable=True: partition 2 (/dev/sdb2) on device /dev/disk/cloud/azure_resource was ntfs formatted and had no important files. Safe for reformatting.
$ grep /mnt /proc/mounts
/dev/sdb1 /mnt ext4 rw,relatime,data=ordered 0 0
[Regression Potential]
The change makes cloud-init accept another situation when it decides
to be reformat a disk. Reformatting of a disk could result in loss of
customer data if the decision to do so results in a false positive.
The fix came with some fairly extensive unit tests (TestCanDevBeReformatted)
on the 'can_dev_be_reformatted' method.
[Other Info]
Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=31b6f1732
=== End SRU Template ===
Some Azure instances such as L32 or G5 have very large ephemeral disks which are partitioned via GPT vs. smaller ephemeral disks that have dos disklabels.
At first boot of an instance the ephemeral disk is prepared and formatted properly. But if the instance is deallocated and then reallocated (thus receiving a new ephemeral disk) then cloud-init does not handle reformatting GPT partition ephemeral disks properly. Therefore /mnt is never mounted again.
Test cases:
1. Deploy an L32(s) VM on Azure
2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
3. Via the portal you can "Redeploy" the VM to a new Azure Host (or alternatively stop and deallocate the VM for some time, and then restart/reallocate the VM).
Expected Results:
- After reallocation we expect the ephemeral disk to be formatted and mounted to /mnt.
Actual Results:
- After reallocation /mnt is not mounted and there are errors in the cloud-init log.
*This was tested on Ubuntu 16.04 - but may affect other releases.
Note: This bug a regression from previous cloud-init releases. GPT support for Azure ephemeral disk handling was added to cloud-init via this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919.
Related bugs:
* bug 1691489: fstab entries written by cloud-config may not be mounted |
|
| 2017-06-12 20:02:19 |
Rakesh Ginjupalli |
bug |
|
|
added subscriber Rakesh Ginjupalli |
| 2017-06-13 18:05:45 |
Brian Murray |
cloud-init (Ubuntu Zesty): status |
Confirmed |
Fix Committed |
|
| 2017-06-13 18:05:48 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-06-13 18:05:52 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-06-13 18:05:59 |
Brian Murray |
tags |
|
verification-needed |
|
| 2017-06-13 18:53:58 |
Brian Murray |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2017-06-13 19:07:30 |
Brian Murray |
cloud-init (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2017-06-22 16:55:42 |
Joshua Powers |
tags |
verification-needed |
verification-done-xenial verification-done-yakkety verification-failed-zesty |
|
| 2017-06-26 15:51:49 |
Joshua Powers |
tags |
verification-done-xenial verification-done-yakkety verification-failed-zesty |
verification-done-xenial verification-done-yakkety verification-done-zesty |
|
| 2017-06-27 15:51:34 |
Launchpad Janitor |
cloud-init (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-27 15:52:22 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-06-27 15:54:02 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-06-27 15:54:45 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-09-23 02:31:47 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2020-12-01 05:23:07 |
Johan Burati |
bug |
|
|
added subscriber Johan Burati |
| 2023-05-10 23:54:59 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2872 |
|
