| 2020-02-02 19:44:09 |
james beedy |
description |
Following controller upgrade, I create a new model. Juju status says this new model gets the upgraded 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. |
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. |
|
