MAAS

  1. Bug #1706196
  2. Comment #10

Comment 10 for bug 1706196

Revision history for this message
Jason Hobbs (jason-hobbs) wrote : Re: when using pods, during juju bootstrap maas creates vm in zone default when a vm already exists in another zone

The same thing affects bundle deployment. We have 3 zones - default, zone2, zone3. juju is asking for a node on zone2, and MAAS, instead of saying it has nothing there, is allocating a VM on pod1. All of the allocations are going to pod1. We have available machines in zone3, but juju never gets to asking for that - MAAS always responds when it asks for zone2 with a newly created vm.

Here's an example request:
Jul 25 22:01:44 infra3 maas.api: [info] Request from user root to acquire a machine with constraints: [('agent_name', ['775df0f6-e0f0-48be-8fa9-7110eece5c5e']), ('zone', ['zone2']), ('tags', ['vm']), ('interfaces', ['peer:space=1;0:space=1;client:space=1;data:space=1;logs:space=1;nrpe-external-master:space=1'])]

In response to this, MAAS is creating a VM on pod1 (always pod1 - even though we have 3 pods).

IMO MAAS should see that there is a tag constraint included and say nothing available matches.