Deleted snapshots still counting against quota

Bug #1173365 reported by Clark Torgerson on 2013-04-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
John Griffith
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:

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

Submitter: Jenkins
Branch: stable/grizzly

commit 93247d22a256db8ed44791343ae942d4f0c40d7f
Author: John Griffith <email address hidden>
Date: Mon Apr 29 11:30:10 2013 -0600

    Fix update snapshot-quotas on delete.

    The merge from stable to RC of the snapshot quota
    fixes missed the new CONF usage and as a result the
    setting was always ignored on delete and therefore
    quotas were not decremented on delete.

    This patch changes CONF back to FLAGS for that call and
    resolves the issue.

    Fixes bug: 1173365

    Change-Id: I7af69d5078ebcc5547e08d543a2dcfd0ca3f6c4b

Thierry Carrez (ttx) on 2013-05-29
Changed in cinder:
milestone: none → havana-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-1 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers