New virtual machine deployments are acquiring stale or used IP addresses from previous deployments in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When deploying new virtual machines, deployment builds fail because the provisioning engine assigns stale or conflicting IP addresses from previous deployments.

In the VMware Aria Automation UI under Assembler > Infrastructure > Resources > Networks > IP Address, an IP address (such as ##.###.###.###) displays as AVAILABLE even though it is actively bound to an existing virtual machine within the vCenter Server inventory.

This desynchronization event forces the deployment engine to generate duplicate allocations, resulting in network address collision faults.

An IP address associated with an existing powered-on deployment is incorrectly marked as available and is being considered for reassignment.

Environment

Aria Automation 8.18.x

Cause

• This issue occurs due to stale resource states inside the VMware Aria Automation provisioning database.
• VMware Aria Automation does not natively reconcile IP allocation changes performed externally within vCenter Server.
• When an active address maintains an AVAILABLE flag with a null binding context inside the internal ipaddress_state collection, it remains inside the free pool space despite being physically in use.

Resolution

Resolution requires database modifications.

To review, analyse & resolve this issue, please contact Broadcom Support and open a support case referencing KB 443837.