This looks like the correct problem statement - the SCSI layer schedules these tasks and so subtle timings could cause disk names to change. This is also we recommend UUIDs or labels or similar to be used in fstab.
The logic for DeviceForIdePort() is based on the fact that our vmbus driver at least knows the order of the disks (IDE or SCSI) that are attached on the Host side. And on Azure, the first IDE disk is always the OS disk, and the second is always the ephemeral disk. That is known and must be the case for all VMs. So in the agent, DeviceForIdePort()[0] always returns the OS disk, and DeviceForIdePort()[1] always returns the ephemeral disk. Ideally cloud- init should use a similar method to auto-detect the ephemeral disk and update fstab if needed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411582 Title: Azure data source should auto-detect ephemeral disk location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1411582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
