This is a known issue affecting vRealize Automation 5.x and 6.x.
Currently, there is no resolution for these versions.
Workaround:
Note: Do not attempt to run the scripts attached to this article on vRealize Automation 7.x versions.
To work around this issue, execute the relevant stored procedure attached to this KB article which is designed to delete hosts and compute resources that are not associated with any active Fabric groups or reservations. This stored procedure will not remove any resources from vRealize Automation that are actively in use.
- Back up your vRealize Automation SQL database.
- Download the RemoveInactiveHosts script attached for the exact version of vRealize Automation.
- Delete any Reservations you have associated with Compute Resources that are associated with the Endpoint you want to delete.
- Install the SQL stored procedure from the RemoveInactiveHosts zip file you have downloaded into your vRealize Automation database.
- Stop any Agents associated with collecting data from the Endpoint.
- Run this SQL query against the vRealize Automation database to retrieve a list of resources that will be removed:
exec usp_RemoveInactiveHosts
- Run this SQL query against the vRealize Automation database to execute the deletions:
exec usp_RemoveInactiveHosts @DeleteFromDB = 1
- After the deletion is complete, attempt once again to delete the endpoint.
- If you still cannot delete the endpoint, you may have active reservations or the compute resource may still be associated with a Fabric group. Start again at step 3.
- After the endpoint is removed, you can start the associated agents and run another data collection to pull any missing hosts back"