Comment 21 for bug 1582323

Hi Bob, you'll see comments to this bug once it is available in
xenial-proposed, and then when it is consequently migrated into
xenial-updates.

On Tue, Jan 31, 2017 at 12:30 PM, Bob Wise <email address hidden> wrote:

> Thanks for the update... how would I check the Xenial queue status? I note
> that "dpkg -l
> grep cloud-init" shows no package on my system.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1582323
>
> Title:
> Commissioning fails when competing cloud metadata resides on disk
>
> Status in cloud-init:
> Fix Released
> Status in MAAS:
> Fix Committed
> Status in MAAS 2.1 series:
> Fix Released
> Status in MAAS trunk series:
> Fix Committed
> Status in cloud-init package in Ubuntu:
> Fix Released
> Status in cloud-init source package in Xenial:
> Confirmed
>
> 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
>

--
Jon Grimm
Engineering Manager, Ubuntu Server
Canonical Ltd