@Stephen, The non-persistence of device names is indeed a bug, even though device names can be declared by cloud-config settings.
With respect to the Azure Linux Agent, it should be noted that one has the option to use a standard declaration of device names (and partitions, if desired), instead of taking the "autodetection" approach. The above option has the advantage that it allows for and/or can allow for a - (persistent) fixation of device names, b - (persistent) configuration of device names (and even partitions, if desired) in waagent.conf, c - removal of multiple lines of code in the waagent script, and it must be emphasized that the above implies that, in essence, the approach of using CustomData for injecting cloud-config settings becomes less relevant or even obsolete, if and only if the waagent script allows for using waagent.conf variables in the cloud-init sequence. In short, there are some possibilities for the improvement of the waagent script and the proper functioning thereof. Kind regards.... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1410835 Title: Azure ephemeral disk and custom mount points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1410835/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
