Bug 1516757

Summary: Provisioning VMs via lifecycle can go over quota if value in automate method is invalid
Product: Red Hat CloudForms Management Engine Reporter: Vatsal Parekh <vparekh>
Component: DocumentationAssignee: Red Hat CloudForms Documentation <cloudforms-docs>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.0CC: abellott, adahms, cpelland, gmccullo, hhudgeon, jhardy, jprause, lavenel, mkanoor, obarenbo, tfitzger, vparekh, yrudman
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: testathon
Fixed In Version: Doc Type: Known Issue
Doc Text:
At current, provisioning virtual machines via life cycle can exceed quota if a value in the Automate method is invalid. As a workaround, ensure that all values specified in or passed to the Automate method are valid.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-26 04:07:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
group qouta schema
none
quota max vms none

Description Vatsal Parekh 2017-11-23 11:10:15 UTC 
Description of problem:
Provisioning VMs bia lifecycle can go over quota if value in automate method is invalid, so it break the functionality of quota
For example, if we set the max_cpus field to 0.5 which is supposed to be an int, the quota is not honored and can provision any number of CPUs

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

How reproducible:


Steps to Reproduce:
1.Edit the quota method with invalid input
2.Provision a VM over the quota
3.

Actual results:
Quota not exceeded where it should have been

Expected results:


Additional info:
Comment 3 William Fitzgerald 2017-12-08 20:10:55 UTC 
Created attachment 1365018 [details]
group qouta schema
Comment 4 William Fitzgerald 2017-12-08 20:11:56 UTC 
Created attachment 1365019 [details]
quota max vms
Comment 5 William Fitzgerald 2017-12-08 20:13:47 UTC 
Vatsal,

Quota is working properly.  This field is defined as an integer.
Quota is seeing a value of 0 and not enforcing quota. 


<AEMethod limits> Getting Quota Values for Model: max_vms Tag Name: quota_max_vms
[----] I, [2017-12-08T13:36:10.914035 #46134:55b0324]  INFO -- : <AEMethod limits> Final Quota Value: 0

Attached is the quota configuration and the schema.

I need to ask the UI team if they are able to validate these fields, keeping in mind that if the substitution flag is on, they would have to allow the datatype and the substitution strings.

Thanks

Billy
Comment 7 Andrew Dahms 2018-07-26 04:07:24 UTC 
The issue in this bug has since been documented as a known issue.

Closing.