juju status does not show true juju version following controller upgrade

[james beedy]

Following controller upgrade, I create a new model. Juju status says this new model gets the new juju version of the controller, but it isn't actually true yet.

$ juju upgrade-juju
best version:
    2.7.1
started upgrade to 2.7.1

$ juju status
Model Controller Cloud/Region Version SLA Timestamp
controller localhost-localhost localhost/localhost 2.7.1 unsupported 19:27:20Z

Machine State DNS Inst id Series AZ Message
0 started 10.222.139.228 juju-41e697-0 bionic Running

$ juju add-model newnew
Added 'newnew' model on localhost/localhost with credential 'localhost' for user 'admin'

$ juju status
Model Controller Cloud/Region Version SLA Timestamp
newnew localhost-localhost localhost/localhost 2.7.1 unsupported 19:28:01Z

Model "admin/newnew" is empty.

$ juju deploy .
ERROR charm's min version (2.7.1) is higher than this juju model's version (2.7.0)

Giving a few minutes this issue resolves itself and the model appears to recognize that it is the new version.

[Tim Penhey (thumper)]

You are entirely right.

The model version shown in status is the version that it is heading towards. In the yaml output there is the versions of all the agents.

I wonder if we should show something like this in the status output for model version while the upgrade is going on:

2.7.0 -> 2.7.1

This would be easy to determine by finding the oldest agent version for the units / machines, and if different to the model version, show the arrow.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.