bootstrap failure with MAAS doesn't tell me which node has a problem
Bug #1591379 reported by
Jason Hobbs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I tried to bootstrap with juju2 and maas2, and got this failure:
ubuntu@
Creating Juju controller "local.
Bootstrapping model "controller"
Starting new instance for initial controller
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
ERROR failed to bootstrap model: cannot start bootstrap instance: unexpected: ServerError: 400 BAD REQUEST ({"storage": ["Mount the root '/' filesystem to be able to deploy this node."]})
It doesn't tell me which node it tried to boot strap on, so I don't know which one I need to go look at to fix.
Changed in juju-core: | |
status: | New → Triaged |
tags: | added: maas-provider usability |
Changed in juju-core: | |
importance: | Undecided → Medium |
tags: | added: papercut |
tags: | added: oil-2.0 |
tags: | added: bitesize |
Changed in juju-core: | |
milestone: | none → 2.0.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
To post a comment you must log in.
In my case there was problem with configuration of KVM machine. I compose KVM machine using MaaS but default storage layout was set in MaaS configuration to: "No storage (blank) layout". When I changed storage layout configuration of KVM machine (in my case I changed it to "LVM") Juju started to add machine to model and deploy it as usual. My MaaS version is "2.9.2 (9165-g.c3e7848d1)" and Juju version is "2.9.10- ubuntu- amd64" on Ubuntu 20.04.2 LTS.