destroying a primary service does not cause subordinate to depart

Bug #1025478 reported by Clint Byrum
6
This bug affects 1 person
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-relation-broken on nagios for the mysql<->nagios connection, but I never get a departed event for the nrpe unit that was just removed.

Changed in juju:
status: New → Confirmed
importance: Undecided → High
Curtis Hovey (sinzui)
Changed in juju:
status: Confirmed → Triaged
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.