block device mappings for deleted instances are leaked
Bug #1069099 reported by
Eoghan Glynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Folsom |
Fix Released
|
Medium
|
Eoghan Glynn | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When an instance is deleted, the corresponding entries in the block device mappings table are not marked as deleted.
To confirm, simply run this SQL fragment (or the equivalent for postgres/sqlite):
echo "select id, deleted, instance_uuid from block_device_
This could cause an issue in large deployments with lots of churn in volume-backed instances, as the extraneous BDM entries wouldn't be picked up by scripted removal of rows marked for deletion.
Changed in nova: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
milestone: | none → grizzly-1 |
status: | New → In Progress |
tags: | added: folsom-backport-potential |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
tags: | removed: in-stable-folsom |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/14580
Review: https:/