juju-upgrade from 2.1.2 to 2.3.2 fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Tim Penhey |
Bug Description
# Issue
In the pursuit of a workaround for lp#1746265 and the recommendation of Rick in #juju-dev, I tried upgrading 3x HA juju controllers from 2.1.2 directly to 2.3.2.
As with lp#1746265, it seems that the juju environment becomes unusable and stuck in an upgrading state though from seemingly other reasons if I'm interpreting the controller machine logs correctly.
I managed to reproduce this every time both on MAAS and LXD.
# How to reproduce on LXD
* juju bootstrap lxd # with juju 2.1.2 client
* juju enable-ha
* juju upgrade-juju -m controller --agent-version 2.3.2 # with juju 2.3.2 client
Here's a repository with a Vagrant machine with steps to reproduce for LXD.
# Logs
See attached machine logs from a MAAS reproduction.
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Forgot link to repository: https:/ /github. com/szeestraten -ntnu/juju- 2.1.2-to- 2.3.2-upgrade