kernel-packages team mailing list archive

[Dan Watkins <daniel.watkins@xxxxxxxxxxxxx>]

So in addition to a kernel fix, we will first need to release a cloud-
init that will handle the endian-ness of instance IDs changing
underneath it.

This is because the kernel is already out in the wild, so we will have
some instances that have booted with the new UUID and the kernel fix
will also trigger the behaviour seen in this bug.

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

Status in cloud-init package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.

  This recent kernel patch in the Ubuntu kernel corrects the endianness
  for some SMBIOS fields, but also has the effect causing cloud-init to
  think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

  The impact is that cloud-init attempts to reprovision the VM, often
  causing the customer to lose access to their VM.

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