bootstrap failure with MAAS doesn't tell me which node has a problem

[Jason Hobbs]

I tried to bootstrap with juju2 and maas2, and got this failure:

ubuntu@juju-test:~/openstack-base$ juju bootstrap vpil-maas-controller vpil-maas
Creating Juju controller "local.vpil-maas-controller" on vpil-maas
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.

[Alex (borsik)]

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.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.