Comment 0 for bug 1828076

When trying to deploy a bundle where machines section looks like this:

'''
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}
  ...
  "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}
  ...
  "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}
'''

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=existing
because we added manually machine id "0" using the command:

juju add-machine --constraints "tags=infra,spaces=space-mgmt,space-api,space-sta" ssh:user@IP

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