HCX Site Pairing displays "Pending" status in Connector UI after upgrade to 4.11.3
search cancel

HCX Site Pairing displays "Pending" status in Connector UI after upgrade to 4.11.3

book

Article ID: 428929

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • After upgrading the HCX Manager from version 4.11.0 to 4.11.3, the Site Pairing status may appear as disconnected in the Connector UI.
  • Attempts to resolve this using the re-registration API (referencing KB 321629) result in the status changing to Pending in the Connector UI, while the Cloud UI may incorrectly report the status as Connected.
  • Site Pairing status stuck in "Pending".
  • Inconsistency between Connector UI and Cloud UI status.
  • Target HCX Manager /common/logs/admin/app.log entries showing JobRecovery workflows.

<timestamps> UTC [main-EventThread, , , TxId: ] INFO  c.v.v.hybridity.recovery.JobRecovery-
--------------[ Job (########-####-####-####-########) with no Active Subflows ]-------------------
{
     "jobId": "########-####-####-####-########",
     "state": "BEGIN",
     "jobType": "RAVJob",
     "lastUpdated": "<timestamps> UTC",
     "parentJobId": "########-####-####-####-########",
     "parentState": "COMPLETED",
     "recoverable": true,
     "workflowType": "ForceCancelRAVTargetWorkflow",
     "previousState": "UNDEFINED_STATE",
     "parentPreviousState": "FORCE_CANCEL_ON_LOCAL"
}

 

Environment

VMware HCX

 

Cause

  • The target HCX Manager is overwhelmed by JobRecovery flows (specifically ForceCancelRAVTargetWorkflow) following the upgrade.
  • This high volume of recovery tasks prevents the site-pair re-registration API requests from being processed immediately.

Resolution

Do not attempt repeated re-registration calls, as this may increase the task backlog.

  1. Monitor the recovery progress by reviewing the /common/logs/admin/app.log on the target HCX Manager.

  2. Allow sufficient time for the existing JobRecovery workflows to complete.

  3. Once the recovery background tasks have subsided, re-issue the site-pair re-registration API call.

  4. Verify that the Site Pairing status transitions to Connected in both the Connector and Cloud UIs.

Additional Information

For more details on the diagnostic process for site pairing, refer to: