Clear leadership settings if service reduced to 0 units
Bug #1642478 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
Bug Description
An application using leadership will usually fail if it is reduced to 0 units, and then more units added.
One of the newly added units will be leader, but will see old settings. These leadership settings will likely be invalid, referring to units that no longer exist. However, the new leader does not know this - for all it knows, these units exist but have not yet been related with the new leader.
Is there a use case for preserving leadership settings once an application has been reduced to 0 units? If not, purging the leadership settings at this point will remove a class of bugs that are difficult or impossible to fix at the charm level.
| Changed in juju: | |
| importance: | Undecided → Wishlist |
| tags: | added: canonical-is |
| Changed in juju: | |
| status: | New → Triaged |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.