juju deploy fails because no machines can be found in MaaS in a given AZ
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When trying to deploy a bundle where machines section looks like this:
'''
machines:
machines:
"0": {constraints: tags=infra zones=AZ1, series: *series}
"1": {constraints: tags=infra zones=AZ1, series: *series}
"2": {constraints: tags=infra zones=AZ2, series: *series}
"3": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"4": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"5": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"6": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"7": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"8": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"9": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"10": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"11": {constraints: tags=os-cs-vnf zones=AZ1, series: *series}
"12": {constraints: tags=os-cs-vplus zones=AZ1, series: *series}
"13": {constraints: tags=os-cs-vplus zones=AZ1, series: *series}
"14": {constraints: tags=os-cs-vplus zones=AZ1, series: *series}
"15": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"16": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"17": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"18": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"19": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"20": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"21": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"22": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"23": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"24": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"25": {constraints: tags=os-cs-vnf zones=AZ2, series: *series}
"26": {constraints: tags=os-cs-vplus zones=AZ2, series: *series}
"27": {constraints: tags=os-cs-vplus zones=AZ2, series: *series}
"28": {constraints: tags=os-cs-vplus zones=AZ2, series: *series}
"29": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"30": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"31": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"32": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"33": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"34": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"35": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"36": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"37": {constraints: tags=os-cs-vplus zones=AZ3, series: *series}
"38": {constraints: tags=os-cs-vnf zones=AZ3, series: *series}
"39": {constraints: tags=os-cs-vplus zones=AZ3, series: *series}
"40": {constraints: tags=os-cs-vplus zones=AZ3, series: *series}
'''
No machines can be found in AZ1 from Maas and deploy fails.
Machines in AZ2 and AZ3 are added correctly.
The deploy is run with option --map-machines=
because we added manually machine id "0" using the command:
juju add-machine --constraints "tags=infra,
This machine is supposed to be in AZ1 but the availability is not correctly showed in juju status.
We are using:
Juju version 2.5.4-xenial-amd64
tags: | added: canonical-bootstack |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
There isn't enough information here to do any debugging from the Juju point of view.
Are you able to provide a list of potential machines from MAAS?
It is also somewhat unclear what the underlying problem is.
Is it that the bundle doesn't deploy?
Is it that the initial machine you have added doesn't show the right zone?
It is possible that the machine you added isn't in zone AZ1 because you didn't ask for it to be in AZ1.
Unless we are able to see all the potential machines from MAAS with their tags, zone, and spaces, there is no way we'd be able to match up the behaviour of Juju to what someone might do manually.