© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
More input.
I today upgraded the controller from 2.9.37 -> 2.9.38
juju upgrade-controller
That worked.
From there, I normally upgrade all models with this command:
for m in $(juju models --all --format json | jq -r '.models[
It basically loops over all models in the controller and tries to upgrade them.
This works - partially and the output looks like this the first round.
e444c390-
best version:
2.9.38
started upgrade to 2.9.38
e444c390-
best version:
2.9.38
started upgrade to 2.9.38
2c7a52c8-
no upgrades available
997bd7de-
best version:
2.9.38
started upgrade to 2.9.38
ERROR cannot find tool version from simple streams: creating environ for model "controller" (2eb4342a-
ERROR some agents have not upgraded to the current model version 2.9.37: machine-0, machine-3, unit-besu-0, unit-prysm-beacon-1
cdccba01-
best version:
2.9.38
started upgrade to 2.9.38
a68e2aae-
best version:
2.9.38
started upgrade to 2.9.38
... and so on, mixed OK, with ERRORS.
So, I continue to run this command, over and over, until most models are upgraded.
The "certificate errors" goes away in the upgrade (after multiple runs) but eventually, all models are upgraded.
===== Unrelated =====
At this point, only one model remains which gives an error like this:
juju upgrade-model -m d84f172a-
ERROR some agents have not upgraded to the current model version 2.9.37: machine-0, machine-3, unit-besu-0, unit-prysm-beacon-1
So, I introspect the model and see that some agents has lost communications with the controller (See the attached Screenshot):
This is all fine, since the machines in that model are turned off, but I think the "ERROR" should be reduced to WARNING