retype volume got error when max volume limit has arrived

Bug #1504719 reported by wanghao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
wanghao

Bug Description

Create volumes until arriving max volume limit, and then retype one of volumes, cinder will raise error: "VolumelimitExceeded: Maximum number of volumes allowed exceeded for quota 'volumes'". The volume type limit is -1, so this should not get this error under retyping operation.

Test steps:
1. Set the volume limit of quota to 3.
2. Create 3 volumes successfully with volume_type A.
3. Retype one of volumes to volume_type B.
4. Cinder raise this error.

wanghao (wanghao749)
Changed in cinder:
assignee: nobody → wanghao (wanghao749)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/233325

Changed in cinder:
status: New → In Progress
Changed in cinder:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/233325
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c68bc2eb2be41a437390cbd81a499bb0ea94f180
Submitter: Jenkins
Branch: master

commit c68bc2eb2be41a437390cbd81a499bb0ea94f180
Author: wanghao <email address hidden>
Date: Sat Oct 10 11:18:02 2015 +0800

    Retyping volume got error under max vol limit

    After reaching the max volume limit and
    retyping one of volumes, cinder will raise
    error: "VolumeLimitExceeded".

    This error shouldn't be occurring since the
    volume type limit is -1 and retyping doesn't
    change the volume quota, it changes the volume
    type quota.

    Change-Id: I5f25c47158ac24bef94078457a84248daa67e80f
    Closes-Bug: #1504719

Changed in cinder:
status: In Progress → Fix Released
wanghao (wanghao749)
Changed in cinder:
milestone: none → mitaka-2
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/cinder 8.0.0.0b2

This issue was fixed in the openstack/cinder 8.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.