destroying a primary service does not cause subordinate to depart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
I am working on some enhancements to nagios and this scenario came up.
nagios == lp:~clint-fewbar/charms/precise/nagios/add-monitors-2
mysql == lp:~clint-fewbar/charms/precise/mysql/add-monitors
nrpe == lp:~clint-fewbar/charms/precise/nrpe/trunk
juju deploy nagios
juju deploy mysql
juju deploy nrpe
juju add-relation nrpe mysql
juju add-relation nrpe:monitors nagios:monitors
juju add-relation mysql:monitors nagios:monitors
This configures nagios to monitors mysql-0 using both nrpe and straight remote mysql pings.
Then I want to clean this up:
juju destroy-service mysql
This properly fires the monitors-
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in juju: | |
status: | Confirmed → Triaged |
importance: | High → Low |