MAAS

Bootstrap failed on MAAS 1.9

Bug #1501607 reported by Mark Shuttleworth on 2015-10-01

This bug report is a duplicate of: Bug #1494476: MAAS provider with MAAS 1.9 - /etc/network/interfaces "auto eth0" gets removed and bridge is not setup. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	MAAS	New	Undecided	Unassigned

Bug Description

MAAS 1.9 first test, first bug :)

Tags:

Revision history for this message

Mark Shuttleworth (sabdfl) wrote on 2015-10-01:

landscape-openstack-autopilot-logs-2015-10-01T06-37-37Z.tar.gz Edit (464.9 KiB, application/x-tar)

Revision history for this message

Adam Collard (adam-collard) wrote on 2015-10-01:

Starting new instance for initial state server
Launching instance
- /MAAS/api/1.0/nodes/node-3aa71978-61df-11e5-b954-000e1e989680/
ERROR failed to bootstrap environment: bootstrap instance started but did not change to Deployed state: instance "/MAAS/api/1.0/nodes/node-3aa71978-61df-11e5-b954-000e1e989680/" failed to deploy

Dean Henrichsmeyer (dean) on 2015-10-01

information type:	Proprietary → Public
affects:	landscape → maas

Revision history for this message

Andres Rodriguez (andreserl) wrote on 2015-10-01:

Hi Mark,

This is due to a bug in Juju, which has been release noted in [1]. The Juju team is working on getting this resolved. As a work around, Juju config needs to be passed:

disable-network-management: true

Doing so, however, will prevent the creation of LXC containers. I'm marking this bug as duplicate of LP: #1494476.

[1]: http://maas.ubuntu.com/docs/changelog.html#known-problems-workarounds