Comment 2 for bug 1669834

We have actually started working on the solution in December 2016. Essentially, the plan was to have model have a state which could be something more descriptive like "updating", "coming up, "migrating", etc... The api calls and user commands will be blocked until the model reports active state but the error message that user will see during "busy" stage will be indicative of why the model is actually un-usable yet.

This work has been de-prioritized and stalled since.