Subordinate units won't die until all principal relations are gone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
Juju appears to not destroy any of a subordinate's units until all of the subordinate application's principal relations are destroyed. This is unfortunate when you eg. want to remove nrpe from a service before destroying just that service, in order to avoid false alerts.
Tested on Juju 2.0.2, 2.1.1 and 2.1.2:
juju deploy cs:ubuntu
juju deploy cs:ubuntu ubuntu2
juju deploy cs:nrpe
juju add-relation ubuntu nrpe
juju add-relation ubuntu2 nrpe
# Wait for both subordinate units to deploy.
juju remove-relation ubuntu nrpe
# Notice that both subordinates are still alive.
juju remove-relation ubuntu2 nrpe
# Both subordinates die.
This doesn't affect single principal applications with multiple units; multiple principal applications seem required to trigger the bug.
Changed in juju: | |
milestone: | none → 2.2-rc1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Christian Muirhead (2-xtian) |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
The removed relation is gone from the DB (though the relationscopes look to still be present), and adding a new unit to its principal leaves you with inconsistent subordinates between the units of that principal.