Upgrade when a machine is offline caused unexpected version

Bug #1834108 reported by Xav Paice on 2019-06-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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/juju/tools/ containing a jujud from the client (2.4.7), with a FORCE-VERSION file set to

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/juju/tools/2.5.7-xenial-amd64, and fixed the machine-0 symlink, and edited the database:

db.settings.update({_id:"9e22b9cb-5333-4722-87aa-df9656ec7fe7:e" }, {$set: {"settings.agent-version": "2.5.7"}})

Then restarted the machine agent.

I'd prefer the original upgrade command to have failed rather than upload a binary with an incorrect version.

Tim Penhey (thumper) on 2019-10-14
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: upgrade-controller upgrade-juju
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers