balawiz's Accepted Solutions

Seems, we can't access the HTML5 client with Cluster URL. So, I performed the following steps to correct the login issue and connected to one of the vRO server HTML5 client. However, please note ... See more...
Seems, we can't access the HTML5 client with Cluster URL. So, I performed the following steps to correct the login issue and connected to one of the vRO server HTML5 client. However, please note that vRO control center is working fine with cluster URL. Log in to the vRealize Orchestrator appliance using SSH or console. Reset the authentication provider by running this command: /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication Unregister and Re-register the vRA from vRO control center authentication provider Restart the orchestrator configurator service by running this command.      service vco-configurator restart --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.
By creating vmware ticket the issue has been resolved. They have cleared the stuck requests for that particular blueprint deployment by running following commands in vRA select br.id, br.sta... See more...
By creating vmware ticket the issue has been resolved. They have cleared the stuck requests for that particular blueprint deployment by running following commands in vRA select br.id, br.status,br.created_date from comp_bprequest br, comp_deployment d where br.dep_id = d.id and d.name = 'Deployment name' order by br.created_date desc; The above command show one progress operation. The following commands has been ran further to resolve BEGIN; select br.id, br.status, br.created_date from comp_bprequest br, comp_deployment d where br.dep_id = d.id and d.name = 'Deployment name' order by br.created_date desc; update comp_bprequest br set status = 'SUCCEEDED' from comp_deployment d where br.status = 'IN_PROGRESS' and br.dep_id = d.id and d.name = 'Deployment name'
The following thread helped me. https://communities.vmware.com/thread/601249
By checking with VMware support, re-installed the vRA agent to the template and deployed. The issue is not recurring so far.