Re-onboarding the VM fails because it is still listed as "Managed" in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Even after the VM is unregistered and deleted from Aria Automation, it is still available under

Service Broker >> Consume >> Virtual Machine >> Managed

• When trying to re-onboard the VM, process fails because the VM still appears in the "Managed" section of Aria Automation.

Environment

VMware Aria Automation 8.x

Cause

The Aria Automation Catalog database holds a stale entry for the VM, which incorrectly lists it as a "Managed" resource.

Resolution

The stale VM entry, improperly listed as a "Managed" resource, can be removed by executing the query below on the VMware Aria Automation database.

Prerequisites
Note: Take snapshots or backups of all VMware Aria Automation nodes as a precautionary measure before proceeding.

Procedure

• SSH to one of the VMware Aria Automation appliances and log in as root.

• Connect to the VMware Aria Automation Catalog Database:

Run the following command to connect to the database using the vracli tool:

vracli dev psql catalog-db;

• Get the VM-Resource-ID using any of the below option:

Option 1 : Using the REST API
GET https://AriaAutoFQDN/deployment/api/resources?search=VM-Name001

Note:
Replace AriaAutoFQDN with the FQDN of your Aria Automation environment.
Replace VM-Name001 with the affected VM name.
Note the ID retrieved from the API

Option 2 : From Aria Automation UI.
Access Service Broker >> Consume >> Virtual Machine >> Managed
Select the VM name and Custom Properties.
Get ID "resourceId" property.

• Update the origin of VM to DISCOVERED:

update dep_resource set origin = 'DISCOVERED' where id = 'VM-Resource-ID';"

• Confirm the VM is mapped under Service Broker >> Consume >> Virtual Machine >> Discovered.
  
  
• Re-initiate the Onboarding task.