Mass-controller is not boot-strapping

Creating Juju controller “maas-controller” on maas-one/default Looking for packaged Juju agent version 2.9.29 for amd64 Located Juju agent version 2.9.29-ubuntu-amd64 at Launching controller instance(s) on maas-one/default… ERROR failed to bootstrap model: cannot start bootstrap instance in availability zone “default”: failed to acquire node: No available machine matches constraints: [(‘agent_name’, [‘a62a1aae-9b08-458a-8ac3-efd12d3816e1’]), (‘mem’, [‘3584’]), (‘tags’, [‘juju’]), (‘zone’, [‘default’])] (resolved to “mem=3584.0 tags=juju zone=default”)

@hridyesh, apologies for a lack of reply til now. Hopefully you’ve found help before now or been able to move forward.

It’d be helpful to know what config was giving to juju bootstrap when it was called in this case.

Going from the data above, juju wasn’t able to find a machine in the MaaS with the tag juju, which had 4Gb of memory. 4Gb is the minimum requirement for a controller machine with juju. Other units may run on machines with less memory if needed.