juju addmodel takes time to see the space in MaaS

I forgot to mention that I tested this in beta5.

We are discussing how to improve this experience.

Currently, we run spaces discovery as part of model initialization: there is a worker that starts up once its dependencies are available. However, there are number of different workers that run at this same time. It's possible that space discovery worker waits for other workers to come up.

from what I can tell, there is going to be a delay as the workers start for a new model, and then it takes ~5s for the various queries to execute against maas and be turned into DB records.

Arguably we should not return from AddModel before its really ready to be used. We could potentially pre-seed the spaces known about in the model if we know the credentials, etc match an existing model. We could also just do some hypothetical direct "model.EnsureComplete()" as part of creating the model, before returning the reference to the new object.

Certainly we switched 'bootstrap' to be synchronous for the same reason (it isn't very useful to do bootstrap and try to do the next step when nothing will actually work yet).

I doubt we can get this in for 2.1 final, but we can focus on it early in 2.2.

We will not be able to address this in 2.2 due to capacity and time constraints - I am moving it into the next milestone: 2.3.

Meanwhile, as a workaround, please add a sleep in the script to ensure that there is sufficient time for space discovery after a model has been added. From comment # 3, anything over 5s should work :D

https://github.com/juju/juju/pull/7383