Volume Quota calls going to Nova instead of Cinder
Bug #1095876 reported by
Gloria Gu
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Unassigned | ||
Folsom |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
openstack is folsom
using cinder volume
how to reproduce:
login as admin
create a project and assign a 1000 for the volume quota
create a user with admin role in horizon and assign that project
login as that user
try to create more than 10 volumes
it will complain about exceeding the limit
workaround
in cinder.conf add the following line:
quota_volumes=1000
quota_gigabytes
restart cinder...then it is ok.
summary: |
- will not honor large volume quota for a project + Volume Quota calls going to Nova instead of Cinder |
To post a comment you must log in.
in addition to modifying the cinder.conf, you can also use the cinder command in place of the nova command.
If you run nova quota-update (tenant-id) --gigabytes=100000, you will see the quota updated in nova, but running cinder quota-show (tenant-id) will not reflect this.
running cinder quota-update (tenant-id) --gigabytes=100000 will also work.
horizon should probably use the cinder quota and not the nova quota in the UI so it's not misleading.