The particular error that it is mentioning is that MAAS is telling us that we can use machine “xh88qk” but it is failing to get to Deployed state, where we can actually expect it to run software on it.
You could try using “juju bootstrap --keep-broken” which will skip the step where we tear down the machine after we feel it has failed to start. Which would potentially let you ssh to the machine and look at files like
/var/log/cloud-init-output.log to see if there was a clear problem while starting the machine.
Looking at your MAAS UI, it looks like there is only a single machine which it could possibly provision. (At least, I think New means it hasn’t finished doing a commissioning step, and Rescue mode probably cannot be provisioned. Leaving only ‘juju-controller.maas’, though that is likely what you want.)
I don’t know if this part is relevant, but it appears you have a
But the juju-controller.maas is only in the
Potentially you would want to do:
juju bootstrap ... --model-default default-space=Juju
--bootstrap-config to make sure that the controller is being set up correctly.