[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** Changed in: maas Status: Fix Committed => Fix Released -- 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

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.10.1 --- cloud-init (0.7.9-0ubuntu1~16.10.1) yakkety; urgency=medium * debian/copyright: update License field to include Apache-2.0 * debian/update-grub-legacy-ec2: fix to include kernels whose config has

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.04.2 --- cloud-init (0.7.9-0ubuntu1~16.04.2) xenial-proposed; urgency=medium * debian/update-grub-legacy-ec2: fix shell syntax error. (LP: #1662221) cloud-init (0.7.9-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** Changed in: maas/2.1 Status: Fix Committed => Fix Released -- 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

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1 --- cloud-init (0.7.9-0ubuntu1) zesty; urgency=medium * New upstream snapshot. - release 0.7.9 - doc: adjust headers in tests documentation for consistency. - integration test: initial commit of integration

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This is fixed in cloud-init 0.7.9 ** Changed in: cloud-init Status: Fix Committed => Fix Released -- 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

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** Also affects: maas/2.1 Importance: Undecided Status: New ** Also affects: maas/trunk Importance: Critical Status: Triaged ** Changed in: maas/trunk Milestone: 2.0.0 => next ** Changed in: maas/trunk Milestone: next => 2.2.0 ** Changed in: maas/2.1 Milestone:

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

re-opening this for cloud-init as the change in cloud-init actually regressed the behavior. ** Changed in: cloud-init (Ubuntu) Status: Fix Released => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Released => Confirmed ** Changed in: cloud-init Status:

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This is fixed in cloud-init 0.7.7 ** Changed in: cloud-init Status: Fix Committed => Fix Released -- 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

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

fix is now released to xenial under bug 1595302. daily cloud-images with this newer version of cloud-init should appear in the next few days. Any image with a serial number *newer* than 20160707 should have cloud-init at 0.7.7~bzr1246-0ubuntu1~16.04.1 . ** Changed in: cloud-init (Ubuntu Xenial)

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial)

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

This bug was fixed in the package cloud-init - 0.7.7~bzr1227-0ubuntu1 --- cloud-init (0.7.7~bzr1227-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - fix one more unit test to run inside buildd. -- Scott Moser Sat, 04 Jun 2016 20:55:07 -0400

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** No longer affects: cloud-init ** Changed in: maas Status: Triaged => In Progress ** Changed in: maas Importance: High => Critical ** Changed in: maas Assignee: (unassigned) => Blake Rouse (blake-rouse) ** Changed in: maas Milestone: None => 2.0.0 -- You received this

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

It was recommended by smoser to add this to MAAS: http://paste.ubuntu.com/16683033/ But then it was discovered that will not handle all cases. A kernel parameter would be needed to force only one datasource. ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in:

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

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 **