Comment 16 for bug 1785314

So reading through this again, the issue is that Juju reads the list of
spaces from MAAS and grabs the ids for those spaces. And the "undefined"
space always has Id = -1. When Juju makes a request of MAAS for a machine,
it always passes the Ids for the spaces rather than the names, and it turns
out that "undefined" can't be passed by Id.
And while certainly the recommendation is to use defined spaces, rather
than undefined, since newly provisioned machines that have not otherwise
been tuned come up as "undefined" it causes a bit of a problem. We want to
push people towards using spaces, but not require them to configure them,
sounds like we're winding ourselves in knots.

On Mon, Jun 17, 2019 at 10:30 AM Chris MacNaughton <
<email address hidden>> wrote:

> John,
>
> I agree that "undefined" is an unfortunate name, but it is also the
> default space in MAAS if the space is un-named. In the case where
> somebody is trying out MAAS + Juju it is entirely possible that they
> still have the default, undefined, space as well as, potentially, an
> additional space. In that case, the spaces in use would be ["undefined",
> $something_else] .
>
> I agree that actually naming the space would be a better solution but
> "undefined" is actually a space :)
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1785314
>
> Title:
> maas spaces are mis-translated
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1785314/+subscriptions
>