Upgrade when a machine is offline caused unexpected version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
My situation:
The controller (no HA) was at 2.4.6.
The client was 2.4.7 (from the deb).
At some stage, unknown to me at the time, the site lost access to external DNS and any http/https outbound access, meaning apt-get, streams, etc all fail.
I ran `juju upgrade-juju -m controller --agent-version 2.5.7` expecting to get an upgrade, but because of the lack of access to the Internet this didn't work.
What happened is that the controller machine-0 agent got a /var/lib/
This didn't complete the upgrade, and agents unable to connect.
To fix, we copied the 2.5.7 jujud from a working site to /var/lib/
db.settings.
Then restarted the machine agent.
I'd prefer the original upgrade command to have failed rather than upload a binary with an incorrect version.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: upgrade-controller upgrade-juju |
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.