Error: " Internal Server Error 500" while trying to do a VM deployment

Products

• VCF Automation

Issue/Introduction

• When attempting to request or interact with a catalog item, the request fails with an HTTP 500 Internal Server Error.
• We can see the below errors from services-logs/prelude/catalog-service-app/file-logs/catalog-service-app.log:
  
   ERROR catalog-service-app [host='catalog-service-app-##########-qnfjl' thread='http-nio-8000-exec-10' user='####' org='########-####-####-####-########324a' trace='############################6caa'] c.v.s.webmvc.error.RestExceptionHandler - API error 500 with response {"message":"404 Not Found: \"{\"message\":\"404 Not Found from GET http://<vco-services-fqdn>:8280/vco/api/actions/org.####/GetProjectName\"}\" [Error Reference ID: ########-####-####-####-########71b8]","statusCode":500,"errorCode":0,"referenceId":null}
com.vmware.symphony.webmvc.error.exception.InternalErrorException: Internal Server Error [Error Reference ID: {########-####-####-####-########ffca}]
        at com.vmware.symphony.webmvc.error.exception.InternalErrorException.wrap(InternalErrorException.java:36)
        at com.vmware.symphony.webmvc.error.RestExceptionHandler.wrapExceptionAndLog(RestExceptionHandler.java:199)
        at com.vmware.symphony.webmvc.error.RestExceptionHandler.handleApiFailures(RestExceptionHandler.java:158)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)

Environment

VMware Aria Automation 8.18.X

Cause

The issue happened because the catalog item configuration includes a dependency on Aria Orchestrator (vRO) action named GetProjectName under the org.#### module path:
http://<vco-services-fqdn>:8280/vco/api/actions/org.####/GetProjectName

The failure occurs because:

• The specified vRO action (GetProjectName) either does not exist, was deleted, or is missing in the target vRO environment.
• Consequently, the vco-service returns a 404 Not Found response, which causes the catalog-service-app to throw a 500 Internal Server Error and halt the operation.

Resolution

To resolve the issue you can use either of the action plans:

• Import or upgrade to a newer version of the catalog item that has been refactored to remove the dependency on the legacy or missing GetProjectName vRO action.
  
  OR
• Find which vRO workflow is invoked during the failure provisioning
• Check the workflow content and find the included action name is different with the one referred in template
• Change the action name back to the one referred to in the template.