@Deepa,
Please file a new bug.
If possible, get
a.) a serial console log of the boot of the system
b.) ssh into the commissioning mode and run 'cloud-init collect-logs'.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I am facing same issue with very latest verion of MaaS MAAS version:
2.4.0 (6981-g011e51b7a-0ubuntu1~18.04.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when co
I'm experiencing exactly the same problem. Seems to be something weird
with cloud-init that hasn't been fixed in 16.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioni
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To ma
I performed the latest updates and much to my dismay it did not resolve
the issue.
On a whim, putting the node that failed to commission into recovery mode
and then taking back out again resolved it.
So, there is at least a workaround now from the UI that will get a node
into the system, but I wo
Is this fix available in the 16.04 LTS image used by MaaS? Commissioning
fails for me and I'm wondering if this is the reason.
"Can not apply stage config, no datasource found! Likely bad things to
come!"
"Failed to start Apply the settings specified in cloud-config"
--
You received this bug no
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
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 CONFIG_
$ name="$release-test"
$ lxc init ubuntu-daily:$release $name
# change pid 1's command line, which is used by cloud-init
# instead of kernel command line inside a container.
$ cmdline="cc:{'datasource_list': ['MAAS']}end_cc"
$ lxc config set $name raw.lxc "lxc.init_cmd=/sbin/init $cmdline"
$ lxc
In order to verify this on xenial, we'll configure a container to
have cloud-config like MAAS uses on the init command's command line.
Basically, instead of invokin /sbin/init for pid 1, we will use:
/sbin/init cc:{'datasource_list':['MAAS']}end_cc
This is equivalent to booting a full system with
Hello M.Morana, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-0ubuntu1~16.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
** Tags removed: verification-needed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides
** 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 are
Hello M.Morana, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-0ubuntu1~16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Brian,
SRU template added. Sorry.
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ The issue originally reported was that when MAAS attempted to enlist a
+ system by booting it with a remote iscsi disk with intent to have cloud-init
+ utilize the MAAS metadata service, cloud-
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 wrote:
> Thanks for the update... how would I check the Xenial queue status? I note
> that "dpkg -l
> grep c
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
The fix has been uploaded to the Xenial queue, waiting on SRU team. Just
FYI that this is on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing
** Tags added: coreos
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notifications about this bug go to:
ht
Bob,
This is fixed in MAAS the issue is still in the Xenial images. That is
why cloud-init is still marked Confirmed for Xenial as it has not been
SRU'd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I opened a bug (marked as duplicate) here with my details.
https://bugs.launchpad.net/maas/+bug/1645872
I just upgraded to 2.1.3 and attempted to repro. Node commissioning
still fails as before. Appears to be to be marked as fixed for 2.1.3.
Not fixed.
--
You received this bug notification beca
** Changed in: maas/2.1
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
T
@Scott,
Any ETA for SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notifications about this bug go to
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 te
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when compet
This is now re-fixed in trunk
(0b0f254a6935a1b1fff128fa177152dd519e1a3d).
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Ti
** Changed in: maas/2.1
Importance: Undecided => Critical
** Changed in: maas/2.1
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas/trunk
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member o
** Changed in: maas/2.1
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage
** Branch linked: lp:~andreserl/maas/lp1582323_2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notificat
** Changed in: maas/trunk
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To m
** Branch linked: lp:~andreserl/maas/lp1582323
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notifications
** 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: N
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: Fix
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when compet
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)
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)
Import
** Branch linked: lp:~smoser/ubuntu/xenial/cloud-init/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage no
** Branch linked: lp:~smoser/ubuntu/yakkety/cloud-init/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage n
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
** Changed in: cloud-
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notifications about this bug
** 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 received
42 matches
Mail list logo
