HCX HA Sync stuck on "POST_CONFIG_VIX" Timeout.
search cancel

HCX HA Sync stuck on "POST_CONFIG_VIX" Timeout.

book

Article ID: 454297

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • Attempting to Force Sync the HA group fails with the following UI error:

 

 

  • The HCX Manager /common/logs/admin/app.log displays errors indicating a missing vSphere inventory object immediately following the VIX timeout:

 

ERROR c.v.v.h.s.i.h.InitiateHAGroupOperation- haGroupForceSync failed. ... errorMessage:HA Force Sync failed. Configuration Update Failed. Operation timedout in state POST_CONFIG_VIX

ERROR c.v.v.h.GenericVsphereInfrastructureProvider- Failed to update the VcServiceToVimInotify inventory for the cluster compute resource {"value":"domain-c####","type":"ClusterComputeResource"}
com.vmware.vim.binding.vmodl.fault.ManagedObjectNotFound: The object 'vim.ClusterComputeResource:domain-c####' has already been deleted or has not been completely created

 

Environment

  • VMware HCX

Cause

The active HCX Compute Profile contains a stale database reference to a decommissioned vSphere cluster. Because the cluster was deleted from vCenter but remains selected in the HCX Compute Profile, HCX builds a configuration payload targeting a non-existent MoRef ID. Consequently, vCenter rejects the configuration request, causing the VIX injection to time out.

Resolution

 

The stale vCenter inventory object must be unchecked from the HCX database by refreshing the Compute Profile

 

  1. Log in to the HCX Manager UI and navigate to Interconnect > Compute Profiles.

  2. Select the Compute Profile associated with the failing HA Service Mesh and click Edit.

  3. Navigate to the Cluster / Resource Pool step in the wizard.

  4. Important: Review the list of checked clusters. If you have any checked cluster that has been removed from vCenter, ensure it is completely unchecked. (If a cluster was recreated but shares the same name as an old one, uncheck it and check it again to force HCX to capture the new MoRef ID).

  5. Click Continue through the remaining steps and click Finish to save the profile.

  6. Navigate to Interconnect > Service Mesh, select the affected HA Group, and trigger a Resync (or Force Sync). The HA group should now successfully apply the configuration and return to a healthy state.

 

 

Powered by Wolken Software