[Bug 1506187] [NEW] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

Public bug reported:

The Azure datasource currently uses the InstanceID from the
SharedConfig.xml file.  On our new CRP stack, this ID is not guaranteed
to be stable and could change if the VM is deallocated.  If the
InstanceID changes then cloud-init will attempt to reprovision the VM,
which could result in temporary loss of access to the VM.

Instead cloud-init should switch to use the VM Unique ID, which is
guaranteed to be stable everywhere for the lifetime of the VM.  The VM
unique ID is explained here: https://azure.microsoft.com/en-us/blog
/accessing-and-using-azure-vm-unique-id/

In short, the unique ID is available via DMI, and can be accessed with
the command 'dmidecode | grep UUID' or even easier via sysfs in the file
"/sys/devices/virtual/dmi/id/product_uuid".

Steve

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1506187

Title:
  Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions