" Cannot invoke "String.equals(Object)" because "endpoint" is null" when attempting to add a disk to a VM that is onboarded on to Aria Automation
search cancel

" Cannot invoke "String.equals(Object)" because "endpoint" is null" when attempting to add a disk to a VM that is onboarded on to Aria Automation

book

Article ID: 403787

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

adding disk to an onboard VM fails with " Cannot invoke "String.equals(Object)" because "endpoint" is null"
Aria Automation 8.16 and older shows the task fail as "internal server error"

provisioning-service-app.log Logs show: 

2025-07-04T07:23:45.254Z ERROR provisioning [host='provisioning-service-app-{POD_ID}}-sj6mh' thread='xn-index-queries-13' user='tango-blueprint-{TANGO_MIKE}}(ieu31-o-inovate6)' org='{{_ORG_}}' trace='{{TRACE_ID}}' parent='{{PARENT}}' span='{{SPAN}}'] c.v.a.r.b.BlueprintProviderRequestService.lambda$allocateOrSimulateRequest$39:1702 - Failed to get compute from instances
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because "endpoint" is null
....
....
Caused by: java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because "endpoint" is null
at com.vmware.admiral.request.blueprint.BlueprintProviderRequestService.lambda$isAddVsphereDiskRequest$57(BlueprintProviderRequestService.java:2009) ~[provisioning-request-1.6.3-10843-40c89d9.jar:na]
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646) ~[na:na]
... 96 common frames omitted

Environment

Aria Automation 8.18.1

Cause

The onboarded VM is missing __endpointType and __endpointLink under custom properties as these properties did not exist in older release of Aria Automation. 

Resolution

In order to resolve the issue we will need to update the Onboarded VM with the missing proeprties __endpointType and __endpointLink via API.

You will need postman or Bruno or an API compatible client to perform the same. 

  1. for the onboarded VM in question navigate to custom properties > resource ID 
    sample screenshot:
  2. Follow KB https://knowledge.broadcom.com/external/article/346005/ for initial setup of postman or an API compatible client and to grab a bearer token,
  3. Query  the resource ID using API: (GET) https://{{vra_fqdn}}/provisioning/uerp/resources/compute/{{resourceid_from_step1}}
  4. Copy the JSON output, review the json under customProperties, add the missing properties:
    sample:

    The value of key : __endpointLink can be collected by running a GET call on API:  https://{{vra_fqdn}}/provisioning/uerp/resources/endpoints, This needs to be mapped correctly cloud-account where the VM is located.
  5. Use the PUT method to push the JSON data back into the API endpoint.