Skip to main content

 Aria Automation VM provisioning failed during VM allocation phase

https://knowledge.broadcom.com/external/article?articleNumber=389497

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

  • the deployment failed as the provisioning timed out as per configured project settings
  • reviewing provisioning-service logs, logs like the below are repeating until the deployment times out:
    <timestamp> INFO provisioning ... Retrying to create new IPs.
<timestamp> ERROR provisioning ... Exception [java.lang.IllegalArgumentException: Couldn't allocate an IP address for resource /resources/network-interfaces/.... No IP addresses were remaining] thrown when allocating IPs.

    Use this command to tail the logs from the Appliance shell session: 

    vracli logs --service provisioning-service-app -f

Environment

Aria Automation 8.x

Cause

The used Network Profile has an overlapping IP Range and therefor tries to allocate an IP even no IP is available.

Resolution

Open the used Network Profile and review the configured IP Ranges for each Network, to have a better overview click the table header "Start IP Address".

Example given:

IP-Range-1: 192.168.0.10 - 192.168.0.100
IP-Range-2: 192.168.0.20 - 192.168.0.40

The IP-Range-2 shows all addresses are allocated and IP-Range-1 shows IP addresses available.

To review allocated IP addresses, navigate to Infrastructure > Resources > Networks > IP Addresses, then click on the header "IP Address" to order by IP.
You can use the filter to select only the impacted Network Profile.

You should find then for IP-Range-1 addresses 192.168.0.10 - 192.168.0.19 are allocated and also 192.168.0.41 - 192.168.0.100 are allocated. 

In this case there is no free IP available in IP-Range-1 as the available IPs have been used by IP-Range-2.

To resolve the issue please allocate more IP addresses or release unused IPs.

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more