Public bug reported: 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. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Description changed: 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). + 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. + - 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. + - 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. + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686514 Title: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
