This is a known issue affecting VMware Cloud Foundation 3.0. There is currently no resolution.
Workaround:
The following steps can be used to workaround this issue:
Note: Take a snapshot of the SDDC Manager VM prior to starting. The snapshot should be removed once the steps are completed and the issue is resolved.
For a vRealize Automation Deployment:
- ssh to the SDDC Manager VM as the vcf user.
- Issue the following command to collect information related to the failed workflow:
cqlsh --cqlversion=3.4.4 -e "expand on; select id,status,operationstatus from inventory.vra"
Note: You will see output similar to the following:
@ Row 1
-----------------+-------------------------------------------------------------------------------------------------------------------------------
id | ########-####-####-####-########7165
status | ACTIVATING
operationstatus | {"resourceStatus":"ACTIVATING","lastOperation":{"type":"DEPLOY","state":"IN_PROGRESS","taskId":"########-####-####-####-########2e97"}}
Note: Make a note of the id value (########-####-####-####-########7165 in this example) and the taskId value (########-####-####-####-########2e97 in this example) as they will be used in the next step.
- Issue a command similar to the following to update the status and state of the workflow:
cqlsh --cqlversion=3.4.4 -e "update inventory.vra set operationstatus= '{\"resourceStatus\":\"ERROR\",\"lastOperation\":{\"type\":\"DEPLOY\",\"state\":\"FAILED\",\"taskId\":\"########-####-####-####-########2e97\"}}' where id = '########-####-####-####-########7165'"
Notes:
- The resourceStatus value of ACTIVATING is replaced with ERROR and the state value of IN_PROGRESS is replaced with FAILED.
- Replace ########-####-####-####-########7165 with the id value returned in Step 2 and ########-####-####-####-########7165 with the taskId value returned in Step 2.
- Issue the command from Step 2 again. You should see output similar to the following:
@ Row 1
-----------------+-------------------------------------------------------------------------------------------------------------------------------
id | ########-####-####-####-########7165
status | ACTIVE
operationstatus | {"resourceStatus":"ERROR","lastOperation":{"type":"DEPLOY","state":"FAILED","taskId":"########-####-####-####-########2e97"}}
Note: It is normal for the status value to remain as ACTIVE.
- Log out of SDDC Manager UI and then log back in. Navigate to Administration -> vRealize Suite -> vRealize Automation. The option to uninstall will now be visible.
- Click the Uninstall button.
- Correct any issues that were related to the failed vRealize Automation deployment.
- Initiate a new vRealize Automation deployment.
For a vRealize Operations Deployment:
The process for correcting this issue in a vRealize Operations deployment should be nearly identical to the process documented for vRealize Automation. The primary difference is the table in the database where the record is held. For a vRealize Automation deployment, the table is inventory.vra while for vRealize Operations the table is inventory.vrops. Any command referencing the inventory.vra table would need to be updated to reference the inventory.vrops table.