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:
Created attachment 1365018 [details] group qouta schema
Created attachment 1365019 [details] quota max vms
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
The issue in this bug has since been documented as a known issue. Closing.