| 2012-08-08 13:21:18 |
Rohit Karajgi |
description |
I checked out the latest Nova code
(Commit: https://github.com/openstack/nova/commit/a418654b070c63c4bed5e3e5523fb947934626f9)
Steps:
1. Login to Dashboard as an admin and set quotas for your your project.
2. Try creating instances for that tenant greater than the set quotas
Expected: Quota exceeded messages after an attempt to create instance once the quota limit is reached
Actual: Instances greater than the allowed quota were created
I checked the database entries after performing the above steps. The instances and cores usages were above the hard limits.
http://paste.openstack.org/show/20052/
This was reproducible for any quota resource (instances, cores, ram etc.)
Besides checking this manually, the Tempest Whitebox tests that test the quota functionality also captured these failures:
http://paste.openstack.org/show/20051/ |
I checked out the latest Nova code
(Commit: https://github.com/openstack/nova/commit/a418654b070c63c4bed5e3e5523fb947934626f9)
Steps:
1. Login to Dashboard as an admin and set quota limits for your project.
2. Try creating instances for that project greater than the set quota limits.
Expected: Quota exceeded messages after an attempt to create instance once the quota limit is reached
Actual: Instances greater than the allowed quota were created
I checked the database entries after performing the above steps. The instances and cores usages were above the hard limits.
http://paste.openstack.org/show/20052/
This was reproducible for any quota resource (instances, cores, ram etc.)
Besides checking this manually, the Tempest Whitebox tests that test the quota functionality also captured these failures:
http://paste.openstack.org/show/20051/ |
|
