Deleting Instances Doesn't Delete Security Group Associations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Anthony Young |
Bug Description
When an instance is deleted, corresponding security_
This becomes a serious performance issue for highly active projects that add and remove instances with great frequency. On Nebula, one highly active project takes over 23 seconds to perform a describe-groups call, and several minutes for run-instances to return to the api caller.
Some related issues:
* The SecurityGroups.
* Deleting a security_group does not delete related security_
Related branches
- Soren Hansen (community): Approve
- Thierry Carrez (community): Approve (gfe)
- Devin Carlen (community): Approve
- Rick Harris (community): Approve
-
Diff: 150 lines (+68/-13)3 files modifiednova/db/sqlalchemy/api.py (+14/-2)
nova/db/sqlalchemy/models.py (+5/-1)
nova/tests/test_compute.py (+49/-10)
Changed in nova: | |
assignee: | nobody → sleepsonthefloor (sleepsonthefloor) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → bexar-rc |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | bexar-rc → 2011.1 |
status: | Fix Committed → Fix Released |