Amogh, work with Alex on this one.
Verified this bz on 5.7.0.16.20161213213754_1ad3545. Steps followed to verify this bz: 1. configured ldap/ext_auth_ipa authentication on both remote and global appliances. 2. login as admin user to remote appliance and add provider and wait for cfme to collect provider data. 3. login as "ldapuser/ipauser" to global appliance and try to provision a vm or change the power state of existing vm. 4. Observe the vm operation is successful. 5. check the remote appliance for vm operation event, and observe that the "ldapuser/ipauser" is auto created on remote appliance. refer screenshot "remote_appliance_success" for user auto created and for the provisioning notifications.
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-2017-0012.html