I have been struggling to get the vapi to work in vro 7.1. I am able to add the metamodel and the endpoint without issue, but whenever I try to run any examples I get
Workflow execution stack:
***
item: 'List all metamodel services/item2', state: 'failed', business state: 'null', exception: 'HTTP response with status code 400 (enable debug logging for details): (Workflow:List all metamodel services / Scriptable task (item1)#7)'
workflow: 'List all metamodel services' (9d3c08d7-0d40-4178-944a-6294d4c29e03)
| 'attribute': name=errorCode type=string value=HTTP response with status code 400 (enable debug logging for details): (Workflow:List all metamodel services / Scriptable task (item1)#7)
| 'input': name=endpoint type=VAPI:VAPIEndpoint value=dunes://service.dunes.ch/CustomSDKObject?id='ENDPOINT--https___XXXXX.XXXX.XXX'&dunesName='VAPI:VAPIEndpoint'
| 'no outputs'
*** End of execution stack.
I was not able to see the added vapi modules in the api explorer either. I tried rebooting, restarting service, etc. I then updated the vapi plugin to the 7.4 version and now I see the added modules in the api explorer, however I still get the 400 error with any workflows.
Hi,
In this particular workflow, at line #7 (the error location) there is the call to vAPI service list() method. Unfortunately, it is not easy to troubleshoot these types of errors with only vRO logs.
As a first step, I'd suggest to look if there are more details in vAPI endpoint logs. They are probably under /storage/log/vmware/vapi/endpoint. BTW, which type of vAPI endpoint do you use (vCenter server, etc.) and which version?
Also, sometimes there are some criptic errors due to some misconfiguration. When you ran the workflow to import vAPI metamodel and register vAPI endpoint, what format of the endpoint URL did you use - https://server.domain.com/api or something else?
I used this format, https://server.domain.com/api
We are running 6.0u3
I will look for those logs, thanks!