Thanks Scott for the thorough explanation. To answer your question: I don't know that there is any such property. I'm asking around to see if there is, but let's assume 'no' for now. Aside from resize, we run into the same situation after a VM needs to be moved to another node. In that case, the ephemeral drive is also recreated (and reformatted ntfs). So any indication we decide to rely on should include this situation. The common factor is that the disk is completely new.
I think you're right that we might need to wait for the disk to appear. I assume that b) was done for other reasons than this bug, or perhaps to not delay mounting too long? An alternative could be to actively unmount the ntfs partition before mkfs. Of course that comes with its own host of race conditions, but the success rate may be higher. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611074 Title: Reformatting of ephemeral drive fails on resize of Azure VM To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1611074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
