Error: "Timeout in remote operation after 80 seconds." when opening the Provisioning Diagram for a deployment in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Aria Automation hangs when trying to open provisioning diagrams, shows a timeout message and does not display. Example errors:
  • Timeout in remote operation after 80 seconds. Operation GET http://10.#.#.#:8282/provisioning/request-graph?contextId=<UUID_pair>
  • Request timed out, please try reloading the page
• Deployment of cloud templates may take a long time in the ALLOCATION stage.

Environment

VMware Aria Automation 8.18.1

Cause

Using a large number of resource pools within a single Cloud Zone will cause performance and scalability issues.

 

Resolution

To scale efficiently, we recommend reducing the number of resource pools within a single cloud zone, which may need to be listed multiple times per request:

• Network profiles without subnets can be deleted.
  
  • Contact Broadcom support referencing this article (#442052) for assistance with identifying such objects 
• Map the Cloud Zone to vSphere Clusters instead of the individual resource pools, if these RPs are much greater in number.
  • This will drastically reduce the provisioning diagram complexity.
• Resource Pool Segmentation: If you strictly must use resource pools, divide these pools across multiple distinct Cloud Zones.
  • By assigning a specific Project to a single, smaller Cloud Zone, Aria only evaluates a fraction of the resources.
  • This reduces blueprint request graph complexity and significantly accelerates network allocation.

 

As a test you can create a single test-cloud-zone with a single resource pool and a test-project and try to deploy a blueprint to this project.
If you monitor the network allocation time and the provisioning diagram complexity, you can compare to the existing large cloud zone.