juju2: no maas nodes available: error message mentions 'zone=default'

[David Britton]

dpb@helo:slaves[0]$ juju bootstrap virtue-dpb virtue
Creating Juju controller "local.virtue-dpb" on virtue
Bootstrapping model "admin"
Starting new instance for initial controller
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
ERROR failed to bootstrap model: cannot start bootstrap instance: cannot run instances: cannot run instances: ServerError: 409 CONFLICT (No available node matches constraints: zone=default)

dpb@helo:slaves[0]$ juju show-cloud local:virtue
defined: local
type: maas
auth-types: [oauth1]
endpoint: http://10.0.7.8/MAAS/

Notice, my bootstrap mentioned nothing about 'zone' in it, nor does my cloud. Furthermore, freeing up a node in another zone and juju started the controller just fine. I think the error message is simply misleading.

[Cheryl Jennings (cherylj)]

It is a misleading message, from the juju user perspective. It looks like it's coming straight from MAAS, though. Maybe there's something Juju can tack on for clarity, or display something else that's more user friendly if we get that error.

[David Britton (dpb)]

On Wed, Apr 27, 2016 at 05:00:52PM -0000, Cheryl Jennings wrote:
> It is a misleading message, from the juju user perspective. It looks
> like it's coming straight from MAAS, though.

Should it be targeted at maas too?

--
David Britton <email address hidden>

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.