Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1327722 - provisioning error in $evm.execute('create_provision_request', *args)
provisioning error in $evm.execute('create_provision_request', *args)
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.5.0
All All
high Severity high
: GA
: 5.5.5
Assigned To: Drew Bomhof
Milan Falešník
ldap:automate:provision
: ZStream
Depends On: 1322876
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-15 14:17 EDT by John Prause
Modified: 2016-07-26 11:32 EDT (History)
9 users (show)

See Also:
Fixed In Version: 5.5.5.2
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, provisioning with the out of the box admin account was successful but provisioning with an ldap user failed. This was because the logic in the create_provision_request (ultimately the class method from_ws_ver_1_x in miq_provision_virt_workflow.rb) was modified as part of the tenant work to validate the requested user_name value existed in the database so the request could be assigned to the proper user/group/tenant. This update now uses lookup_by_identity to validate a user parameter and the issue is now resolved.
Story Points: ---
Clone Of: 1322876
Environment:
Last Closed: 2016-07-26 11:32:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1488 normal SHIPPED_LIVE CFME 5.5.5 bug fixes and enhancement update 2016-07-26 15:28:27 EDT

  None (edit)
Comment 4 Milan Falešník 2016-07-18 05:18:42 EDT
Verified that the user resolution using both name and name@domain works in 5.5.5.2

I user the username and it correctly found out the user in AD. The created user in the Access Control has name@domain in there. Then I tried it again with the name@domain and it worked too.
Comment 6 errata-xmlrpc 2016-07-26 11:32:32 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1488.html

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