yahoo-eng-team team mailing list archive

[Dan Watkins <daniel.watkins@xxxxxxxxxxxxx>]

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Changed in: cloud-init
       Status: New => In Progress

** Changed in: cloud-init
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Xenial)
     Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Precise:
  New
Status in cloud-init source package in Trusty:
  New
Status in cloud-init source package in Vivid:
  New
Status in cloud-init source package in Wily:
  New
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  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

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