Removing a machine should remove any series-upgrade side-effects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
2.7 |
Fix Released
|
High
|
Unassigned | ||
2.8 |
Fix Released
|
High
|
Unassigned |
Bug Description
The following sequence of events has been observed:
- A series upgrade is commenced.
- The upgrade cannot progress, probably due to https:/
- The machine is removed.
- There remains a lock document for the the machine in machineUpgradeS
- Leadership that was pinned for applications with units on the machine remains pinned.
If the pinned leader for an application was one of the units on the removed machine, this can mean an application with no leaders, and no units able to successfully claim leadership.
When the leadership pinning facade was conceived during the implementation of series upgrades, it was anticipated that there might be future client exposure of the functionality. This might be something to consider, but at very least a removed machine should properly clean up after itself.
summary: |
- Removing a machine should remove any series-upgrade locks + Removing a machine should remove any series-upgrade side-effects |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
assignee: | Joseph Phillips (manadart) → Simon Richardson (simonrichardson) |
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
Changed in juju: | |
milestone: | 2.9-rc1 → 3.0.0 |
Changed in juju: | |
assignee: | Simon Richardson (simonrichardson) → nobody |
Changed in juju: | |
milestone: | 3.0.0 → 3.0-beta1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
status: | Fix Released → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
This is one possible cause for the symptoms observed here: /bugs.launchpad .net/juju/ +bug/1858693
https:/