© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I'm seeing this in a similar (but not the same) env. As in the case above, I have machine #0 which is added via ssh before deploying the bundle:
$ juju add-machine --constraints "tags=infra,
$ juju deploy --debug ./$BUNDLE0 --map-machines=
This results in "suitable availability zone for machine X not found" messages for all AZ1 nodes, even though in fact there are plenty of nodes avail. in Maas in AZ1.
juju status: https:/
Minimal test bundle: https:/
> Are you able to provide a list of potential machines from MAAS?
Here:
$ maas maas-root nodes read zone=AZ1 | jq -r '.[] | "\(.system_id) \(.zone.name) \(.tag_names)"' | sort
6cpceq AZ1 ["physical"
8kwayw AZ1 ["physical"
d3cp3w AZ1 ["physical"
dxbn87 AZ1 ["physical"
eka6sd AZ1 ["physical"
ew8rw3 AZ1 ["physical"
ffbbse AZ1 ["physical"
gdrhba AZ1 ["physical"
h3pf8x AZ1 ["physical"
hawfsg AZ1 ["physical"
kgfkrc AZ1 ["physical"
rcmmkm AZ1 ["physical"
wtrfwr AZ1 ["physical"
x7dkdm AZ1 ["physical"
xqswcf AZ1 ["virtual","juju"]
yp83ae AZ1 ["physical"
> It is also somewhat unclear what the underlying problem is.
>
> Is it that the bundle doesn't deploy?
Right, the bundle doesn't deploy as it's missing nodes from AZ1.
The expectation would be that upon bundle deploy juju recognizes the machine #0 already added machine and request the additional machines named in the bundle.
If it helps, here are TRACE logs from the controller: https:/