Preventing Network Allocation Errors for deployments using AWS Fargate in VMware Aria Automation 8.x that uses resourcehelpers

Products

• VMware Aria Suite

Issue/Introduction

• Customers may encounter the following error when attempting a Day 2 network allocation update for an AWS Fargate resource managed by VMware Aria Automation:
  NetworkAllocationService errors with a UnsupportedOperationException
  • This error occurs when adding new networks to an AWS serverless compute component and using Day 2 Operations in Aria Automation to update it.

Symptoms:

• The network allocation update fails during the Day 2 Operation.
• The provisioning-service logs capture the following error:
  Error in operation PUT /resources/network-allocations/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: java.lang.UnsupportedOperationException
• Existing AWS Fargate deployments cannot be modified to include additional network allocations.

Environment

 

• VMware Aria Automation 8.x
• AWS Fargate

 

Cause

The UnsupportedOperationException occurs because of how network allocation helpers manage networking resources during provisioning.

1. Network Allocation Helpers Allocate All Resources Simultaneously

   • During initial provisioning, all network allocation helpers are processed at once to ensure compliance with affinity and anti-affinity rules.
   • When a new network is added, the allocation helper attempts to reallocate all previously assigned resources, which can cause conflicts.

2. Reallocation Can Cause Unexpected Placement Issues

   • If the system allowed reallocation, the previously allocated networks could change in ways that impact other dependencies.
   • To prevent unintended disruptions, the system blocks reallocation attempts and throws an UnsupportedOperationException.

3. Deprecation of Allocation Helpers

   • Allocation helpers are scheduled for deprecation, meaning no new functionality will be added or prioritized in VMware Aria Automation 8.x.
   • Future versions of Aria Automation will not support modifying allocations via allocation helpers, reinforcing that changes must be handled externally.

Resolution

Work Within Existing Allocation Rules

• Avoid modifying network allocations for AWS Fargate resources after deployment.
• If a new network is required, redeploy the resource with the correct network configuration.

Redesign Deployment Strategy

• Instead of modifying network allocations, create a new AWS Fargate resource that includes the updated network.
• Utilize infrastructure-as-code (IaC) principles to manage network configurations upfront before deployment.

Deprecation of Allocation Helpers

• Allocation helpers are scheduled for deprecation, meaning no new functionality will be added or prioritized.
• Customers should transition to alternative integration methods that do not rely on allocation helpers for AWS Fargate.

Prevent Future Errors by Updating Policy Configurations

• Remove the Day 2 Action policy for network updates to prevent users from triggering this error in the existing version.
• Any networks that must be added to AWS Fargate resources should be managed outside the scope of VMware Aria Automation 8.x.

Validation Steps

1. Verify the Day 2 Action policies in Aria Automation and ensure that the network update option is disabled for AWS Fargate resources.
2. Confirm that AWS Fargate networking is managed at deployment time rather than through updates.

Additional Information

• The UnsupportedOperationException is intentional to prevent network reallocation issues that could disrupt existing deployments.
• As allocation helpers will be deprecated, modifying AWS Fargate resources within Aria Automation is not supported beyond the initial deployment.