upgrade-series hangs, leaves lock behind

Bug #1855013 reported by Xav Paice on 2019-12-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

Running 2.6.10, Xenial.

I ran juju upgrade-series 12 prepare bionic, which looked to have completed the hooks but then hung for 20+ mins. I ended up ctrl-c'ing the command.

This left a lock behind, preventing retry of the prepare, and preventing complete:

https://pastebin.canonical.com/p/9ptW9CX9Yy/

Fixed with:

db.machineUpgradeSeriesLocks.update({ "_id" : "55ab2ebd-6e66-4d23-8549-aee9f03fae13:12" }, { $set: { "machine-status" : "prepare completed" } } )

Is there a better way to do this? Two things come to mind - firstly, don't ctrl-c, I should have spent more time digging into what was hanging. Second, we could do with a retry or a force option, in case I wasn't running this in a tmux and lost my session to the controller (which happens when we work remotely).

Changed in juju:
status: New → Triaged
importance: Undecided → High
Changed in juju:
milestone: none → 2.8-beta1
milestone: 2.8-beta1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers