Bug 1516757 – Provisioning VMs via lifecycle can go over quota if value in automate method is invalid

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1516757 - Provisioning VMs via lifecycle can go over quota if value in automate method is invalid

Summary:	Provisioning VMs via lifecycle can go over quota if value in automate method ...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Documentation (Show other bugs)
Sub Component:
Version:	5.9.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	GA
Target Release:	5.9.0
Assigned To:	Red Hat CloudForms Documentation
QA Contact:	Red Hat CloudForms Documentation
Docs Contact:

URL:
Whiteboard:	testathon
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-23 06:10 EST by Vatsal Parekh
Modified:	2018-07-26 00:07 EDT (History)
CC List:	13 users (show)

See Also:
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 00:07:24 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core

Attachments	(Terms of Use)
group qouta schema (291.24 KB, image/png) 2017-12-08 15:10 EST, William Fitzgerald	no flags	Details
quota max vms (334.70 KB, image/png) 2017-12-08 15:11 EST, William Fitzgerald	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Vatsal Parekh 2017-11-23 06:10:15 EST

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 15:10 EST

Created attachment 1365018 [details]
group qouta schema

Comment 4 William Fitzgerald 2017-12-08 15:11 EST

Created attachment 1365019 [details]
quota max vms

Comment 5 William Fitzgerald 2017-12-08 15:13:47 EST

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 00:07:24 EDT

The issue in this bug has since been documented as a known issue.

Closing.

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