Aria Automation shows Original Task Error: 'Provisioning operation failed' . The connection with vAPI endpoint can not be established. Please make sure the vAPI endpoint is running in the vCenter.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)
• VMware vRealize Automation 8.x

Issue/Introduction

When running an action , workflow , or deployment operation, you encounter an error message similar to : 

Extensibility triggered task failed , Original Task Error: 'Provisioning operation failed. The connection with vAPI endpoint can not be established. Please make sure the vAPI endpoint is running in the vCenter. 

Environment

Aria Automation 8.x

Cause

The error message "Original Task Error: 'Provisioning operation failed. The connection with vAPI endpoint can not be established. Please make sure the vAPI endpoint is running in the vCenter.'" clearly indicates that Aria Automation cannot establish a connection to the vAPI endpoint service running on your vCenter Server.

Resolution

Check these steps on vCenter Server:

1. vAPI Endpoint Service is Down or Not Running on vCenter Server:

   • Cause: The service responsible for the vAPI endpoint within vCenter Server has stopped or failed to start.
   • Troubleshooting:
     1. SSH to your vCenter Server Appliance (VCSA).
     2. Run service-control --status to list all services and their status. Look for a service related to vapi or vmware-vapi-endpoint.
     3. If it's stopped, attempt to start it: service-control --start vmware-vapi-endpoint.
     4. Monitor the service status. Check vCenter logs (/var/log/vmware/vapi/) for errors if it fails to start.
     5. Verify the overall health of your vCenter Server through the VAMI interface (https://:5480).

 

Check these steps from Aria Automation: 

1. Incorrect vCenter Endpoint Configuration in Aria Automation:

   • Cause: The vCenter Server entry configured in Aria Automation (under Cloud Accounts -> vCenter) has an incorrect IP address, FQDN, or credentials.
   • Troubleshooting:
     1. Go to Aria Automation -> Infrastructure -> Connections -> Cloud Accounts.
     2. Select your vCenter Cloud Account and click Edit.
     3. Verify the Host Address (FQDN or IP) is correct and resolvable.
     4. Verify the Credentials are correct and have sufficient permissions on vCenter Server.
     5. Attempt to "Validate" the account.
2. Examine provisioning-service-app.log
   

   • Cause: The provisioning service shows SUSPENDED 
   • Troubleshooting:
     
     1. Open and Access the Aria Automation SSH session on any node 
     2. Change directory using Linux command: cd /service-logs/prelude/provisioning-service-app/file-logs/
     3. Use the 'less' command to search file: less provisioning-service-app.log 
     4. Use the character '/' to pattern search for endpointHealthCheckState=SUSPENDED

 

Additional Information

Check additional documentation and resources related to vAPI endpoint issues:

https://knowledge.broadcom.com/external/article/315492/aria-automation-deployments-utilizing-th.html

https://knowledge.broadcom.com/external/article/312158/vcenter-cloud-account-datacollection-fai.html