Back to bug 1327722

Who When What Removed Added
John Prause 2016-04-15 18:17:33 UTC Depends On 1322876
Drew Bomhof 2016-05-02 20:57:26 UTC Status ASSIGNED ON_DEV
Chris Pelland 2016-05-03 14:12:39 UTC Target Release 5.5.4 5.5.5
Drew Bomhof 2016-05-25 17:55:14 UTC Status ON_DEV POST
John Prause 2016-05-31 14:04:27 UTC Status POST MODIFIED
Marianne Feifer 2016-05-31 16:50:32 UTC CC mfeifer
Doc Text Cause: 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 the requested user_name value existed in the database so the request could be assigned to the proper user/group/tenant.

Consequence: Provisioning with the out of the box admin account is successful but provisioning with a ldap user fails on 5.5.2

Fix: Use lookup_by_identity to validate a user param

Result:
errata-xmlrpc 2016-06-29 14:40:42 UTC Status MODIFIED ON_QA
John Prause 2016-07-13 18:50:03 UTC Fixed In Version 5.5.5.2
Milan Falešník 2016-07-18 09:18:42 UTC Status ON_QA VERIFIED
Suyog Sainkar 2016-07-19 12:26:08 UTC CC ssainkar
Doc Text Cause: 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 the requested user_name value existed in the database so the request could be assigned to the proper user/group/tenant.

Consequence: Provisioning with the out of the box admin account is successful but provisioning with a ldap user fails on 5.5.2

Fix: Use lookup_by_identity to validate a user param

Result:
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.
errata-xmlrpc 2016-07-26 14:44:27 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-07-26 15:32:32 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-07-26 11:32:32 UTC

Back to bug 1327722