Comment 0 for bug 1706196
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote when using pods, during juju bootstrap maas creates vm in zone default when a vm already exists in another zone | #0 |
I am using pods, and have VMs created from those pods in three zones that I've created (zone1, zone2, zone3). There is also a 'default' zone in MAAS, which I'm not allowed to edit or delete, and has no nodes in it.
When I juju bootstrap without a 'zone' placement directive, juju tries first to allocate a vm from the 'default' zone in MAAS. MAAS sees that there is no matching node, then that I'm using pods, and creates a new VM to respond to juju's request for a node.
My expected behavior here is for juju to end up bootstrapping onto one of the existing VMs in one of the zones with nodes in it. I can get that by using a '--to zone=zone1' placement directive, but I shouldn't have to - it should just work and use one of the existing VMs.
This is with juju 2.2.2 and maas 2.2.2 (6094-g78d97d0-