Bug 1248215 - Service : User provisioning request for more than one is not approved with reason " Provisioning limit is set to 1"
Summary: Service : User provisioning request for more than one is not approved with re...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.5.0
Assignee: Greg McCullough
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-29 21:27 UTC by Shveta
Modified: 2017-09-14 11:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-30 13:33:56 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
request (96.97 KB, image/png)
2015-07-29 21:27 UTC, Shveta 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1490825 0 unspecified CLOSED VM provision with Number of VMs>1 is not working 2021-02-22 00:41:40 UTC

Internal Links: 1490825

Description Shveta 2015-07-29 21:27:08 UTC 
Created attachment 1057421 [details]
request

Description of problem:


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


How reproducible:


Steps to Reproduce: 
1. Create a user with group EVM-administrator
2. Login as user and provision more than one VM 
3. request stays in pending status and shows " Request was not auto-approved for the following reasons: (Requested VMs 3 limit is 1) "

Actual results:


Expected results:


Additional info:
5.4.1.0.20150717083323_6ed7e1c
Comment 2 Greg McCullough 2015-07-30 13:33:56 UTC 
The default approval state machine is setup to only auto-approve 1 VM.  You can  remove the value for max_vms (or set to 0) to skip the VM count check.

See automate instance: / ManageIQ / Infrastructure / VM / Provisioning / StateMachines / ProvisionRequestApproval / Default

If this resolves your issue we will close as 'Not a bug'.
Comment 3 Shveta 2015-07-30 17:51:14 UTC 
Yes that resolved the issue.
Thanks
Note You need to log in before you can comment on or make changes to this bug.