Bug 1327722
| Summary: | provisioning error in $evm.execute('create_provision_request', *args) | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
| Component: | Automate | Assignee: | Drew Bomhof <dbomhof> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5.0 | CC: | cpelland, dajohnso, jhardy, jocarter, mfeifer, mkanoor, obarenbo, ssainkar, tfitzger |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.5.5 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | ldap:automate:provision | ||
| 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 15:32:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1322876 | ||
| Bug Blocks: | |||
|
Comment 2
Drew Bomhof
2016-05-25 17:55:14 UTC
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. 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 |