In the CASAdapter logs in Aria Operations for the Automation adapter, a log entry similar to the following is found.
YYYY-MM-DDTHH:MM:SS DEBUG [CASAdapterRelationshipBuilderThread thread 3] (######) com.vmware.adapter3.cas.processor.DeploymentRelationshipProcessor.setStatus - Error while parsing jsonObject for deployment: <Identifier> and resourceName: null
YYYY-MM-DDTHH:MM:SS ERROR [CASAdapterRelationshipBuilderThread thread 3] (######) com.vmware.adapter3.cas.processor.DeploymentRelationshipProcessor.processDeploymentResources - Unable to parse the json response for the deployment <UUID-for-deployment> Failure is with resource Custom.LoadBalancerPersistence Error is
[] org.json.JSONException: JSONObject["endpointType"] not found.
[] at org.json.JSONObject.get(JSONObject.java:568) ~[json-20231013.jar:?]
[] at org.json.JSONObject.getString(JSONObject.java:855) ~[json-20231013.jar:?]
[] at com.vmware.adapter3.cas.processor.DeploymentRelationshipProcessor.processDeploymentResources(DeploymentRelationshipProcessor.java:207) ~[CASAdapter.jar:?]
[] at com.vmware.adapter3.cas.processor.DeploymentRelationshipProcessor.createDeploymentAndResourceRelationship(DeploymentRelationshipProcessor.java:161) ~[CASAdapter.jar:?]
[] at com.vmware.adapter3.cas.processor.DeploymentRelationshipProcessor.process(DeploymentRelationshipProcessor.java:61) ~[CASAdapter.jar:?]
[] at com.vmware.adapter3.cas.processor.RelationshipBuilderTask.run(RelationshipBuilderTask.java:16) ~[CASAdapter.jar:?]
[] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:?]
[] at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
[] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
[] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
[] at java.lang.Thread.run(Unknown Source) ~[?:?]
Aria Operations 8.X
Aria Automation 8.X
The exception is being thrown within the processDeploymentResources method. Based on this, it appears there is an attempt to create or process a custom resource through deployments in vRA (Aria Automation). The vRA (Aria Automation) adapter is intentionally designed to support a defined set of known resource types, such as vCenter VMs, EC2 instances, Azure VMs, and similar objects. The implementation includes additional logic to correlate these resources created through specific endpoints (for example, the vCenter adapter for vCenter VMs and the AWS adapter for EC2 instances).
The endpointType property returned by the vRA API is used to determine the originating endpoint of a resource, particularly since vRA supports multiple integrations.
In the CAS adapter, only a predefined list of object types is supported as children of a deployment. Since the object in this case does not fall within the supported list, the exception is expected behavior.
However, this should not fail the display of the object relationship for all the resources in the entire deployment. If the entirety of the deployment and its object/resources are not displaying in Aria Operations, a different issue is such as the API resource limitation is occuring on this or other deployments from Aria Automation which will affect all deployments after. In this instance, we see the following failure in the same adapter logging before the unsupported resource issue above:
YYYY-MM-DDTHH:MM:SS, ERROR [CASAdapterDataCollectionThread thread 1 >> Organization >> GroupPlacement >> Deployment] (######) com.vmware.adapter3.cas.util.CASAdapterUtil.handleResponse - Error connecting to CAS for URL =https://vrauseutaz1m1.ve.fedex.com/deployment/api/deployments?expandProject=true&expandResources=true&expandLastRequest=true&expandMetadata=true&cloudTypes=vsphere,aws,azure,gcp,vsphere_cloud,azure_ea,vmc,vcd&resourceRefreshStrategy=NONE&apiVersion=2020-01-30&$top=100&$skip=4800 response is, {"message":"Reading more than 100 resources not supported. Use apiVersion 2020-08-25 or higher.","statusCode":400,"errorCode":20063} response code is 400
Generate an Aria Operations diagnostic support bundle, and then create a support case with Broadcom for further support.