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

Bug 1244519

Summary: Failed to create unlimited memory quota limit via REST
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-engineAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: aburden, amureini, dfediuck, gklein, lpeer, lsurette, mavital, mgoldboi, rbalakri, rgolan, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-3.6.1Keywords: Triaged
Target Release: 3.6.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, quota memory limit values could not be set below zero using the REST API, prohibiting unlimited quota behavior. Now, values below zero are converted to '-1' to allow unlimited quota using the REST API.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 01:29:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artyom 2015-07-19 15:07:23 UTC
Description of problem:
Failed to create unlimited memory quota limit via REST

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create cluster limit:
<cluster_quota_limit>
<memory_limit>-1</memory_limit>
<vcpu_limit>-1</vcpu_limit>
</cluster_quota_limit>
2.
3.

Actual results:
Status Code: 500 Internal Server Error

Expected results:
Action success and create quota cluster limit with unlimited memory and vcpu values.

Additional info:

Comment 1 Sandro Bonazzola 2015-10-26 12:35:03 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 2 Artyom 2015-11-29 10:57:57 UTC
Verified on rhevm-restapi-3.6.1-0.2.el6.noarch
Send <cluster_quota_limit>
<memory_limit>-1</memory_limit>
<vcpu_limit>-1</vcpu_limit>
</cluster_quota_limit> via REST works fine