Aria Automation workload Optimization Fails with 'network interface IP assignment [STATIC] allocation failed'

Products

• VCF Automation

Issue/Introduction

During a workload placement event between VCF Operations (Aria Operations) and Aria Automation (vRA),  a live VM relocation and rebalance shows a provisioning-service-app error:

The following log snippet is observed in /var/log/services/prelude/provisioning-service-app.log

Aria Automation Provisioning Service:

network interface IP assignment [STATIC] allocation failed: network profile [<Network_Profile_Name>] has no existing subnets that match the specified IP address [<Static_IP_Address>].




 

Environment

Aria Automation 8.x

 

Cause

Aria Automation requires a full IP static Range defined in the Network Profile Section 

During relocation, the filter re-validates that the target network profile's subnets contain the desired IP within their configured SubnetRangeState ranges. If Aria Automation's Network Profile doesn't explicitly link that subnet to the alternative clusters, or if the IPAM validation fails during the mock allocation, the placement engine throws its hands up and returns an empty whitelist.

This also happens because provisioning service takes longer than the 3.3-minute window because it loops through complex affinity filters that ultimately fail when trying to find a workload with a static IP. The target network profile lacks an IP range covering that specific address, forcing a hard rejection.

Resolution

To stabilize the workload optimization engine and ensure successful placement, review the following  in your Network Profile Filters (Aria Automation)

• Validate, add, and or configure a Subnet Range within the target network profile and subnet(s) that cover the required static IP addresses of the workloads being moved.