Bug 908834 - Quota exhaustion is remembered after first blocked action and thus not allowing any next action below grade limit
Summary: Quota exhaustion is remembered after first blocked action and thus not allowi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Gilad Chaplik
QA Contact: Jiri Belka
URL:
Whiteboard: sla
Depends On:
Blocks: 922807 948448
TreeView+ depends on / blocked
 
Reported: 2013-02-07 16:09 UTC by Jiri Belka
Modified: 2016-02-10 20:15 UTC (History)
10 users (show)

Fixed In Version: sf10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine.log (2.98 KB, application/x-tar)
2013-02-07 16:09 UTC, Jiri Belka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 12014 0 None None None Never

Description Jiri Belka 2013-02-07 16:09:14 UTC
Created attachment 694577 [details]
engine.log

Description of problem:
Quota exhaustion is remembered after first blocked action and thus not allowing any next action on the VM even resources of the VM are then below grade limit.

Running a VM with resources above grace (hard-limit) triggers quota resources exhaustion. This exhaustion is kept remembered. So after being blocked for first time, then when you redefine VM's resources (put them below hard-limit) and then you start the VM again, it is again blocked.

	
2013-Feb-07, 16:52
	
Cluster-Quota limit limit exceeded and operation was blocked. Utilization: mem:0%, Requested: mem:101.07% - Please select a different quota or contact your administrator to extend the quota.

and then...
	
2013-Feb-07, 16:52
	
Cluster-Quota limit limit exceeded and operation was blocked. Utilization: mem:101.07%, Requested: mem:50% - Please select a different quota or contact your administrator to extend the quota.

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

How reproducible:
100%

Steps to Reproduce:
1. on a DC which is in 'audit' quota mode, assign to a user (AD) role 'VmCreator'
2. create some quota with following setup:
   * memory 1024 (soft 60% => 615)
   * cpu 3 (soft 60% => 2)
   * disk 10G (soft 80% => 9)
3. assign to previously used user following role on quota - PowerUserRole
4. assign this user to the quota as consumer
5. login with the user into User Portal
6. create new VM, the VM should inherit valid quota with following resources
   * memory 1035
   * cpu 1
7. run the VM via Run Once with cdrom booting (just to put VM up)
8. check in Admin Portal quota usage
9. run the VM via Run Once with cdrom booting (just to put VM up) with memory 512, cpu 1 (this is below hard-limit)

Actual results:
VM is blocked even it is not overpassing quota hardlimit, it is blocked because previous quota exhaustion is remembered.

Expected results:
If nothing is using quota, then I should be able to run a VM with resources below hardlimit even previous blockage.

Additional info:

Comment 2 Jiri Belka 2013-03-11 16:32:22 UTC
ok, sf10.

Comment 3 Itamar Heim 2013-06-11 08:27:06 UTC
3.2 has been released

Comment 4 Itamar Heim 2013-06-11 08:27:11 UTC
3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:30:42 UTC
3.2 has been released


Note You need to log in before you can comment on or make changes to this bug.