juju reports units in non-existent OpenStack availability zones

[Paul Gear]

When deploying new units to an existing juju 1.25.11 environment, juju reports a non-existent OpenStack availability zone: https://pastebin.canonical.com/197194/

This zone does not exist anywhere in our OpenStack deploy: https://pastebin.canonical.com/197192/

One of the wrong machines is over 18 months old: https://pastebin.canonical.com/197195/, while the other is brand new: https://pastebin.canonical.com/197196/

I suspect this will impact scheduling of multiple unit services onto separate hosts.

[Anastasia (anastasia-macmood)]

@Paul Gear,
"juju" project in launchpad is dedicated to Juju 2x. Are you seeing the same in your Juju 2x controllers?

Meanwhile, I'll add "juju-core" project as affected by this report for 1.25x :D

[Paul Gear (paulgear)]

I tried to put the bug in juju-core, but launchpad wouldn't let me for some reason. This bug applies only to juju 1.x.

[Tim Penhey (thumper)]

Seriously, we aren't looking at doing any other bug fixes on 1.25 just now.