Aria Operations Workload Optimization relocation fails with 500 Internal Server Error when using Bluecat external IPAM

Products

• VCF Operations

Issue/Introduction

When attempting to use Workload Optimization in VMware Aria Operations to relocate a virtual machine (VM) managed by VMware Aria Automation, the placement action fails. The following symptoms are observed:

• Aria Operations logs an error during the placement request.

• A 500 Internal Server Error occurs during the RELOCATE_GET_PLACEMENTS API communication between Aria Operations and Aria Automation.

• Communication may initially look like a generic connectivity failure, but upgrading the appliance or applying patches (such as Patch 4) does not resolve the issue.

• The target virtual machine utilizes static IP assignment.

Environment

 

• VMware Aria Operations

• VMware Aria Automation

• External IPAM (Bluecat Integration)

 

Cause

This issue occurs because the target virtual machine relies on a static IP assignment. When initiating a relocation request, Aria Automation requires that the destination network profile explicitly includes that static IP within its defined network ranges.

When utilizing Bluecat as an external IPAM instead of native Aria Automation subnet ranges, the destination network profile often lacks these defined ranges. Because the static IP cannot be mapped or validated within the destination profile's range, the relocation request fails with a 500 Internal Server Error.

Resolution

To resolve this issue, you must manually configure the matching IP ranges within the Aria Automation network profile so that static IP validation can succeed during relocation.

1. Log in to the VMware Aria Automation console.

2. Navigate to Infrastructure > Configure > Network Profiles.

3. Select and edit the target destination network profile intended for the relocation.

4. Define and add the appropriate IP range that encompasses the static IP address of the virtual machine being relocated.

5. Save the changes.

6. Return to VMware Aria Operations and retry the Workload Optimization relocation request (RELOCATE_GET_PLACEMENTS). The request should now succeed and provide placement recommendations.

Additional Information

If the Workload Optimization placement still fails after updating the network profile, ensure that your underlying vSAN configurations are fully active on the target cluster. A deactivated vSAN configuration can cause a vSAN resync block, which will stop the placement from completing after the network validation succeeds.