Error: "Certificate Differs from the expected one" when trying to Replicate VMs
search cancel

Error: "Certificate Differs from the expected one" when trying to Replicate VMs

book

Article ID: 370266

calendar_today

Updated On:

Products

VMware Cloud Director VMware vSphere ESXi

Issue/Introduction

  • After replacing certificates in VMware Cloud Director Availability services, existing VM replications may fail between sites.
  • When creating a new outgoing replication, the following error is displayed:

    "Unable to find suitable Replicator Service from site ''"

  • Replication synchronization begins successfully but fails after several minutes.
  • Existing replications fail while newly created or reconfigured replications succeed.
  • Synchronization tasks fail with:

    "Sync timeout for replication ''"

  • Tunnel logs may report:

    "Unrecognized client SHA"

  • In /opt/vmware/h4/cloud/log/cloud.log on the VMware Cloud Availability Replication Manager, log entries similar to the following may be observed:

    DEBUG - [UI] [job-59] com.vmware.h4.jobengine.JobExecution resourceName='Service Provider Site'}) completed with result VcloudSiteInfo{apiPublicUrl='null', isLocal=false, state=PeerState{ incomingCommError=null,

    ERROR - [UI] [https-jsse-nio-8443-exec-10] c.v.h.c.c.error.ExceptionAdvisorBase sourceSiteType=vcloud&destinationSiteType=vcloud&site=Tenant-Site failed.

    com.vmware.exception.CertificateMismatchException: java.security.cert.CertificateException: Certificate seen on the network differs from the certificate we expected
    at com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:50)

  • 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

Each VMware Cloud Director Availability service uses a UNIQUE SSL certificate both for the HTTPS access to the service management interface and in the communication with other services. Following certificate replacement, existing replication objects may continue referencing previously learned certificate metadata or trust relationships associated with the old certificate.

As a result existing replications may fail until trust metadata has been refreshed

NOTE: 

A wildcard certificate can be used for the Cloud Service.

Each VMware Cloud Director Availability service must use a UNIQUE certificate identity which differs from other VMware Cloud Director Availability services.

Certificates may be self-signed or CA-signed depending on deployment requirements, though self-signed certificates are commonly used for simplicity.

Do not use the same wildcard certificate for more than one cloud site

Resolution

To resolve this issue, Inspect the VMware Cloud Director Availability interface of both sites.

  • Check if the certificate is valid and not expired.
  • Verify VMware Cloud Director Availability services are NOT using the SAME WILDCARD certificate across multiple components.
  • A wildcard certificate can be used for the CLOUD SERVICE. Each VMware Cloud Director Availability service must use a unique certificate identity.
  • Repair the the two cloud sites.

If repair operations complete successfully but replication synchronization continues failing:

  1. Open the affected replication configuration
  2. Reconfigure or edit the replication object
  3. Save or reinitialise the replication configuration even if no configuration changes are required
  4. Trigger a new synchronization attempt
  5. Monitor synchronisation status

Additional Information

For more details on replacing the services certificates in the Cloud Director site, please see: Replacing the services certificates in the Cloud Director site