Multi-VM Deployments Failing due to Network Selection
search cancel

Multi-VM Deployments Failing due to Network Selection

book

Article ID: 428665

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • When a new request for a single deployment containing multiple VMs is submitted, an error similar to the one listed below is encountered:

    com.vmware.xenon.common.LocalizableValidationException: Compute network component 'Network_1' is allocated to one network 'Example_Network_Subnet01' with link '/resources/sub-networks/########-####-####-####-############', but also attached to machine 'VM_name' NIC 'null' which is assigned to a different network with link '/resources/sub-networks/########-####-####-####-############'. You can use cloud template tag constraints to control network allocation. Allocate to networks that have free IP address space in their IP ranges.

Environment

Aria Automation 8.x

Cause

Overlapping tags could be presenting multiple network selections, and/or the network selected does not have enough IP addresses available for all of the components in the request.

Resolution

Additional Information

In cases where this is not possible, Extensibility using Orchestrator may be required to find and select a single network that has enough capacity for all of the components:
Extending and automating application life cycles with extensibility