[LBaaS] Deletion of associated-to-pool(s) health monitor should fail
Bug #1243129 reported by
Rami Vaknin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Oleg Bondarev |
Bug Description
Version
=======
Havana on rhel
Description
===========
It's possible to delete health monitor while they are associated to one or more pools, I think that this should be prohibited, and dissociation from pool should be required first.
Changed in neutron: | |
assignee: | nobody → Oleg Bondarev (obondarev) |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: lbaas |
Changed in neutron: | |
milestone: | none → icehouse-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
As already discussed in the Havana summit, the current model is very prone to errors.
For example, if the delete fails on one of the association deletes, what would be the correct behavior
a. roll back the deletion - difficult to implement
b. don't delete the HM, until the erogenous association are handled
Also as the association deletion is a-sync, I am not sure that the HM deletion behavior is correct.
Last, update on HM error handling suffers from a similar issue when an error is encountered.
In Havana a change to the model was discussed without eventualy anything happening, we can discuss again at the ice house summit.