Onboarded VM shows IP as "Available" in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After onboarding a virtual machine (VM), the assigned IP address continues to appear as "available" in the IP management system. This leads to the same IP being reassigned to another VM during deployment. As a result, duplicate IP assignments occur, which may cause network conflicts or deployment failures.

Environment

Aria Automation 

Cause

The IP management system fails to update the IP status to "Allocated" after onboarding completes. This causes the system to treat the IP as unallocated, making it eligible for reassignment to another VM. This behavior is suspected to be due to the relocation pods being in an unhealthy state during the initial onboarding

Resolution

1. Verify Relocation Pod Health

Ensure that the relocation pods are in a Running state by executing the following command:

kubectl get pods -n prelude | grep -i relocation

Expected Output (Single Node Example):

relocation-service-app-659698bb6c-5x6dd    1/1   Running   0   34d  
relocation-ui-app-568fd7757d-cvrc4         1/1   Running   0   34d  

Note: In a clustered environment, you should see three pods for each relocation service running across different nodes.

2. Re-onboard the Affected VM

Once you confirm the relocation pods are healthy, proceed to onboard the VM again by following the steps outlined in the official documentation:

🔗 Onboard Machines with Template and Mapping – Broadcom TechDocs

Additional Information

This behavior occurs intermittently and correlates with the health of core platform components like relocation pods.

It is recommended to verify that all pods and services are in a healthy state before performing onboarding operations.