There is a model configuration item, "default-space", which is used as the default binding for all deployments where it is otherwise unspecified. By default, it is "alpha".
In order to accommodate legacy deployments, we do not throw an error when applications are bound to an empty alpha space, rather we treat such a situation as space-agnostic.
What then happens is that the binding information returns the preferred private address of the machine where the unit is deployed. This can only be one address and Juju's selection rules will prefer an IPv4 local-cloud address.
The solution is configure the model's default-space with one of the MAAS spaces.
This is by design.
There is a model configuration item, "default-space", which is used as the default binding for all deployments where it is otherwise unspecified. By default, it is "alpha".
In order to accommodate legacy deployments, we do not throw an error when applications are bound to an empty alpha space, rather we treat such a situation as space-agnostic.
What then happens is that the binding information returns the preferred private address of the machine where the unit is deployed. This can only be one address and Juju's selection rules will prefer an IPv4 local-cloud address.
The solution is configure the model's default-space with one of the MAAS spaces.