"Operation aborted due to an unexpected error." message when creating replications to an On-Premises site in Cloud Director Availability 4.x

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Creating replications from a Cloud to an On-Premises site fails, and you see a message similar to:

Operation aborted due to an unexpected error.

• In the /var/opt/vmware/h4/replicator/replicator.log file on the Cloud Director Availability On-Premises Appliance, you see entries similar to:

2023-05-16 14:06:29.883 ERROR - [UI-dd9cd66d-f961-494e-b0c7-87a2bd388855-r1367-cK-uF-TuP-UJ-bc] [job-23] com.vmware.h4.jobengine.JobExecution     : Task ba616abe-a4dd-4f21-bade-236eb03a1633 (WorkflowInfo{
type='setupDestination', resourceType='replication', resourceId='H4-3d7bce0c-0860-47e9-0f0f-0f0f0f0f0f0f', isPrivate=false, resourceName='null'}) has failed
com.vmware.vlsi.client.exception.VlsiClientException: LS entry not found
 

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue can occur when there are multiple service registrations in the Lookup Service for the Storage Monitoring Service (SMS).

Resolution

To verify you are experiencing this issue, query the Lookup Service for the STS service registration.

1. Log into the vCenter Server/PSC Appliance through SSH or console as root.
2. Change to Bash shell by typing shell and press Enter.
3. Run the following command to get the current sslTrust anchor stored for the vCenter Server:

/usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert --ep-type com.vmware.vim.pbm 2>/dev/null

Example output:
Name: cis.sms.ServiceName
Description: cis.sms.ServiceDescription
Service Product: com.vmware.vim.sms
Service Type: sms
Service ID: 4fdc2cef-840e-4ee8-8174-6901067765d7
Site ID: default-first-site
Node ID: c38bfb70-da78-41d0-a58a-9d96cc1e25a3
Owner ID: [e-mail]
Version: 7.0
Endpoints:
        Type: com.vmware.vim.pbm
        Protocol: https
        URL: https://vcsa-01a.corp.vmw:443/pbm/sdk

Note: The expected result is one STS service entry per site.

If the service registrations have different Service IDs, contact VMware vCenter Server Support and note this Article ID (83820) in the problem description. For more information, see How to File a Support Request.