enable-ha after upgrade 2.9.x to 3.0-beta1 leaves 2 new nodes "ha-status: ha-pending"
Bug #1947175 reported by
Heather Lanigan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
High
|
Heather Lanigan | ||
Bug Description
juju show-controller | grep ha-status
ha-status: ha-enabled
ha-status: ha-pending
ha-status: ha-pending
The new machines did install juju-db from 4.0/stable: 4.0.9
$ sjuju status --format yaml | grep member
controller-
controller-
controller-
To reproduce:
* Bootstrap 2.9.16
* Upgrade to 3.0-beta1 via snap
* Run juju enable-ha
| Changed in juju: | |
| milestone: | 3.0.0 → 3.0.1 |
| Changed in juju: | |
| milestone: | 3.0.1 → 3.0.2 |
| Changed in juju: | |
| milestone: | 3.0.2 → 3.0.3 |
| Changed in juju: | |
| assignee: | nobody → Heather Lanigan (hmlanigan) |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Upgrade controller from 2.9 to 3.0 is not supported. The decision was made after this bug was filed. Allows juju to leave behind old databases among other reasons.