Build Failure After Adding New VLAN Network in Aria Automation Due to Static IP Allocation Error

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After adding a new VLAN-backed network to an Aria Automation environment, provisioning tasks may begin to fail. This typically impacts virtual machine deployments where static IP assignment is configured. The issue prevents successful resource placement and results in deployment failure.

Example Error Message:

Allocation filter error: Unable to find a common placement for compute 'Virtual_Machine' and its associated network resources on region '([region_ID])'. Reason: Network filters: network profile data [[Network profile name [profile], document link [/provisioning/resources/network-profiles/[document_id]], subnets [subnet 10.xxx.xxx.0/24]]], network interface IP assignment [STATIC] allocation failed: Network profile [profile] has no subnets with static IP ranges or ranges do not have available IP addresses.

 

Environment

VMware Aria Automation 8.x

Cause

The build failure occurs because the newly added VLAN network is not fully configured in the corresponding network profile. Common misconfigurations include:

• The subnet for the new VLAN was not added to the network profile

• The subnet is added, but no static IP range is defined

• The static IP range exists but has no available IP addresses

When Aria Automation attempts to provision a virtual machine using this network profile, it cannot allocate a static IP address. As a result, the placement engine fails to find a valid network-compute match and the deployment is aborted.

 

Resolution

To resolve this issue, follow these steps:

1. Check Network Profile Configuration:

   • Go to Infrastructure > Network Profiles in Aria Automation.

   • Select the profile associated with the impacted deployment region or project.

   • Ensure the newly added VLAN-backed network is listed under the subnets section.

2. Verify Static IP Range:

   • Confirm that a valid static IP range is defined for the new subnet.

   • Make sure the IP range has available addresses.

   • If using an external IPAM, validate the IP pool configuration and integration status.

3. Add or Update Subnet as Needed:

   • If the subnet is missing, click Add Network or Subnet, select the correct network, and define the required static IP range.

   • If the subnet exists but lacks an IP range, edit the subnet and input a valid static IP pool.

4. Re-Test Deployment:

   • After updating the network profile, retry the failed deployment.

   • Monitor logs or task history to ensure that static IP allocation succeeds.