Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1650027

Summary: Cinder quota per project is not working
Product: Red Hat OpenStack Reporter: Chen <cchen>
Component: openstack-cinderAssignee: Cinder Bugs List <cinder-bugs>
Status: CLOSED DUPLICATE QA Contact: Avi Avraham <aavraham>
Severity: medium Docs Contact: Kim Nylander <knylande>
Priority: unspecified    
Version: 10.0 (Newton)CC: eharney
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-15 08:04:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chen 2018-11-15 07:57:37 UTC
Description of problem:

Cinder quota per project is not working

Version-Release number of selected component (if applicable):

OSP10

How reproducible:

100%

Steps to Reproduce:

$ cinder quota-update --backups 1000 <projectname>

$ cinder quota-show <projectname> | grep backups
    | backups              | 1000    |

$ openstack quota show <projectname> | grep backups
| backups              | 10                               |

$ openstack volume backup create <volumeid>
ERROR: BackupLimitExceeded: Maximum number of volumes allowed (10) exceeded for quota 'backups'

Actual results:

The default quota is being used when creating backups instead of the project quota.

Expected results:

The quota for project should be used first and then default quota.

Additional info:

Comment 1 Eric Harney 2018-11-15 08:04:19 UTC
This is because quota-update only works with project ids, and not project names.

Try using project ids instead.

This behavior is a known usability problem now, and is described in

https://bugzilla.redhat.com/show_bug.cgi?id=1574431

*** This bug has been marked as a duplicate of bug 1574431 ***