Service mesh Edit or Rsync or both fails with Error: Operation timedout in state POST_CONFIG_VIX.

Products

• VMware

Issue/Introduction

YYYY-MM-DD HH:MM:SS.ms UTC [InterconnectService_SvcThread-19417, SM:servicemesh-cad2daa2-####-####-####-6cb0aceb0f70, IX:8e3d35b6-####-####-####-7a1afe79f7f2, J:57e5742a, , TxId: f3fbf831-####-####-####-28759f125694] ERROR c.v.v.h.s.i.ApplianceLifeCycleJob- ApplianceLifeCycleJob failed in state CHECK_IX_REACHABILITY. Error: Interconnect Service Workflow GenerateAndPostConfig failed. Error: Operation timedout in state POST_CONFIG_VIX.
java.lang.RuntimeException: Interconnect Service Workflow GenerateAndPostConfig failed. Error: Operation timedout in state POST_CONFIG_VIX
        at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.getSubflowJobDataArray(AbstractInterconnectJob.java:758)
        at com.vmware.vchs.hybridity.service.interconnect.ApplianceLifeCycleJob.handleState(ApplianceLifeCycleJob.java:253)
        at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.run(AbstractInterconnectJob.java:217)
        at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
YYYY-MM-DD HH:MM:SS.ms UTC [InterconnectService_SvcThread-19417, SM:servicemesh-cad2daa2-####-####-####-6cb0aceb0f70, IX:8e3d35b6-####-####-####-7a1afe79f7f2, J:57e5742a, , TxId: f3fbf831-####-####-####-28759f125694] WARN  c.v.v.h.s.i.ApplianceLifeCycleJob- Error of unknown type : java.lang.RuntimeException

Environment

VMware HCX

Cause

The configure task is failing due to an MTU configuration error. The MTU value set for the service mesh exceeds what the environment supports, making it invalid.

For example, in this case, the service mesh MTU is configured to 1438, as shown below, 

Note: Discovered MTU is intended as a guidance mechanism; however, in some scenarios, transient network conditions or intermediate devices may result in an MTU value that differs from the actual supported end-to-end MTU. Manual validation is advised.

Resolution

Verify the MTU configured on the affected service mesh and ensure it aligns with the MTU supported by the environment, rather than relying solely on the configured, assumed, or Discovered MTU values.

For example, in this case, the service mesh MTU was configured to 1438, while the environment supports only an MTU of 1400, as confirmed by the customer’s internal networking team and cloud vendor. Based on this confirmation, the MTU was updated from 1438 to 1400, as shown below.

The edit and re-sync operations are now completing successfully.