Comment 2 for bug 1828076

Note that they have a manual machine as machine 0, not a machine recognized
by the provider. (I would guess it does ultimately come from the provider
but we don't have a way to know that as we don't have an instance id).

As a manually provisioned machine, we probably don't track things like AZ
or spaces correctly to line up that machine with the machines listed in the
bundle.

John
=:->

On Wed, May 8, 2019, 06:35 Tim Penhey <email address hidden> wrote:

> 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.
>
> ** Changed in: juju
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1828076
>
> Title:
> juju deploy fails because no machines can be found in MaaS in a given
> AZ
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1828076/+subscriptions
>