Deploying OVF from URL fail in VMware Aria Automation

Products

• VCF Automation

Issue/Introduction

Environment specific:

• The deployment only fails when the OVF https URL is used (deployment from content library works).
• The vCenter server have 500+ Storage Profiles created.

Symptoms:

• Deployment of the Cloud.vSphere.Machines template from a https OVF URL failes with: 'Error Message:  Provisioning operation failed. Read timed out '
• There is no related task visible in the vCenter.

Environment

VMware Aria Automation 8.18.x

VMware vCenter 8.0 U3

Cause

The CreateImportSpec task in vCenter Server performs a request that calls each Storage Profile individually to check where to import the OVF. In environments with a large number of profiles, this sequential processing exceeds the default 120-second timeout configured within the Aria Automation provisioning service.

Resolution

The primary resolution involves a fix on the vCenter Server side that is planned for the next 8.x relates to ensure the CreateImportSpec task retrieves all storage profiles in a single call rather than individually 

Workaround:

Reduce number of Storage Profiles in the vcenter server.

Increase specific timeouts in the Aria Automation provisioning service.

• Connect to one of the Aria Automation nodes using SSH.
• Execute the below command to edit the provisioning service:
  

  kubectl -n prelude edit deployment/provisioning-service-app

• Use the vi editor to add the following option under JAVA_OPTS:
  

  -Dvsphere.client.read.socket.timeout=300000
  -Dvphere.connection.request.timeout.seconds=300000

• Save the configuration and wait until provisioning service restart on all nodes.

NOTE: The workaround is not persistent and after services restart it should be implemented again.