A workflow fails when using a SovLabs workflow that requires vCenter integration. Only seen if more than 1 vCenter endpoint is configured within the vRO environment. SovLabs integrations that require vCenter endpoints include: vSphere Snapshot, VM tagging, vSphere DRS, and any configuration using VMTools as a Connection method.
Error message similar to: "'[Workflow Name]' has failed Vcenter Instance with name '[vCenter Name] already exists!"
The cause is that in the event multiple vCenters existed and the Instance UUID (vimUUID) was not populated on the vCenter Endpoint at the time the SovLabs vCenter endpoint was configured, the logic in the back-end code could not determine the correct vCenter Endpoint to use to perform the integration.
All versions prior to 2019.12.0
Workaround or Solution
There are 2 possible solutions for this issue outlined below.
- Reach out to the Account Manager or https://support.sovlabs.com to obtain the latest SovLabs plugin (newer than 2019.12.0)
- Follow the standard Upgrade Process to install and configure the plugin correctly: http://docs.sovlabs.com/latest/vRA/7.6/getting-started/sovlabs-plugin/upgrade/
- Delete the existing SovLabs vCenter Endpoint from the Deployments Tab.
- Add a new SovLabs vCenter Endpoint. (This will now force the vCenter vimUUID to be populated correctly)
- In vRO check if the vCenter UUID isn't correctly populated on the SovLabs vCenter Endpoint on the resource. Browse in vRO to the Resources > Library > SovLabs > Vcenter resource. Look at the vimUUID value.
If it is empty - obtain the vCenter Endpoint Instance UUID for the vCenter missing the identifier. This can be done by looking at the vCenter endpoint in vRO. Inventory > vSphere vCenter Plug-in > '[vCenterName]' > Instance UUID. (Copy this number)
- Then browse in vRO to the Resources > Library > SovLabs > Vcenter resource. Save the resource to your desktop. Right-Click > Save to file.
WARNING: Before modifying the file it is always recommended to create a second copy as a backup
- Modify the file using a text editor, copy & paste the vimUUID number into the vimUUID field and save the file.
- 'Update' the resource to use the new file in vRO by right-clicking > Update. Validate the XML now correctly shows the vimUUID field populated for the vCenter in question.
See General Release information here: https://support.sovlabs.com/a/solutions/articles/6000213106-release-maintenance