Hi Scott, The linked branch seems to reliably format the ephemeral disk on large instances. However, after redeploying the VM I don't see the ephemeral disk mounted after boot. The cloud-init log does not indicate any error, and if I type 'mount -a' (or do a simple reboot) then the disk is mounted properly with an ext4 filesystem.
To test this I'm creating an L32s VM on Azure with Ubuntu 16.04, updating cloud-init manually from your git branch, and then I click the 'redeploy' option via the portal. I see that the ephemeral disk is partitioned/formatted correctly, but just not mounted. Am I missing some configuration? What is normally responsible for mounting the ephemeral disk once it is formatted? Steve ** Attachment added: "cloud-init.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4877814/+files/cloud-init.log -- 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/cloud-init/+bug/1686514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
