HCX Service Mesh Resync Operation Stuck at 0% Progress
Article ID: 398281
Updated On:
Products
Issue/Introduction
When attempting to resync a VMware HCX Service Mesh by clicking the "Resync" button, the progress indicator remains stuck at 0% indefinitely. This issue occurs on all service meshes in the environment, indicating that it is not tied to a specific HCX manager but appears to be a UI/API functionality problem.
The following symptoms are observed:
- The resync progress never advances past 0%
- No error messages appear in logs
- HTTP Archive (HAR) file analysis shows no API calls being made when the Resync button is clicked, confirming a UI/backend disconnect
- Other HCX operations like IX appliance redeployment and migrations work correctly
- The issue is specific to the direct Resync button functionality
For instructions on how to collect a HAR file to confirm this behavior, see How to Collect a HAR File and HTTP Error Logs.
Environment
- VMware HCX 4.11.0
- VMware vCenter Server 7.x or 8.x
- VMware vSphere ESXi 7.x or 8.x
- Service meshes with overridden uplinks
Cause
The issue is caused by a regression in the HCX 4.11.0 UI code. For service meshes with overridden uplinks, the UI never makes a call to the preview mesh changes API (/hybridity/api/interconnect/serviceMesh/<mesh-id>/generateDiff). As a result, the Resync button remains disabled on the dialog and the operation never progresses.
When the HCX preview service mesh component detects that uplinks are overridden for a mesh, due to a bug in the UI code in 4.11.0, it fails to trigger the necessary API call, causing the resync operation to remain stuck at 0%. This is a UI/API issue rather than an infrastructure or configuration problem.
Resolution
Workaround
Until you can update to HCX 4.11.1 or later, use this workaround:
- Instead of clicking the "Resync" button, click the "Edit" button on the Service Mesh
- Progress through the edit workflow without making any changes
- Complete the edit process to trigger a resync as a side effect of the edit operation
This workaround allows the service mesh to recognize changes and perform a resync operation, even though the direct Resync button functionality is not working.
Resolved in
This issue is fixed in:
- VMware HCX 9.0.0.0
- VMware HCX 4.11.1 (and later)
Update to one of these versions to resolve the issue.
If the error persists after upgrading to HCX 4.11.1 or later, please collect and provide the following when contacting Broadcom Support:
- A HAR file capturing the failed resync attempt (see the link provided in the Issue/Introduction section)
- Complete HCX manager logs with database dump checked. For instructions, see Gather Technical Support Logs
Additional resources for opening and managing support cases:
Feedback
