yahoo-eng-team team mailing list archive

[Blake Rouse <blake.rouse@xxxxxxxxxxxxx>]

Scott,

What can MAAS do to tell cloud-init that its should use the MAAS
datasource first and always in the enlistment and commissioning
environment. We don't want cloud-init to look at the disk first in the
case of MAAS.

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

** Changed in: maas
       Status: New => Triaged

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: maas
   Importance: Undecided => High

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

Status in cloud-init:
  Confirmed
Status in MAAS:
  Triaged

Bug description:
  A customer reused hardware that had previously deployed a RHEL
  Overcloud-controller which places metadata on the disk as a legitimate
  source, that cloud-init looks at by default.  When the newly enlisted
  node appeared it had the name of "overcloud-controller-0" vs. maas-
  enlist, pulled from the disk metadata which had overridden MAAS'
  metadata.  Commissioning continually failed on all of the nodes until
  the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f
  data or dd zeros to disk).

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