Deleted snapshots still counting against quota
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith | ||
Grizzly |
Fix Released
|
High
|
John Griffith |
Bug Description
It appears that both deleted snapshots and GB used are not being updated in the database though listing through the 'cinder' tool confirms that snapshots have been deleted. This appears to be related to the following bug and appears to not have been included in Grizzly: https:/
As an example: We had a quota of 1 TB used and a test instance of 300 GB. We successfully took two snapshots and then were rightly denied a third. However, upon deleting the snapshots, we continued to receive the "quota exceeded" error when trying to take further snapshots. Though listing via the 'cinder' tool shows no snapshots, the DB shows a count of multiple snapshots and 1500 GB used.
Changed in cinder: | |
importance: | Undecided → High |
assignee: | nobody → John Griffith (john-griffith) |
status: | New → Triaged |
status: | Triaged → Fix Committed |
Changed in cinder: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-1 → 2013.2 |
Fix proposed to branch: stable/grizzly /review. openstack. org/27731
Review: https:/