Unable to proceed. Appliance Name: <Service_Mesh_Name>-IX-I1, Blocking Service: RAVService, Reason: Operation not allowed as appliance has ongoing RAV Migrations.
/common/logs/admin/app.log on the Source HCX Manager:2026-05-20 05:56:53.611 UTC [InterconnectService_SvcThread-135, J:29####70, , TxId: e9####79-b##0-4##7-a##5-4e4b####b866] ERROR c.v.v.h.s.i.InitiateServiceMeshOperation- deleteServiceMesh failed, errorCode:null. stacktrace:null, errorMessage:Unable to proceed. Appliance Name: <Service_Mesh_Name>-IX-I1, Blocking Service: RAVService, Reason: Operation not allowed as appliance has ongoing RAV Migrations.
2026-05-20 05:56:53.611 UTC [InterconnectService_SvcThread-135, J:29####70, , TxId: e9####79-b##0-4##7-a##5-4e4b####b866] ERROR c.v.v.h.s.i.InitiateServiceMeshOperation- Failure detected while verifying completion of InterconnectServiceJobs::deleteServiceMesh. Reason: Interconnect Service Workflow deleteServiceMesh failed. Error: Unable to proceed. Appliance Name: <Service_Mesh_Name>-IX-I1, Blocking Service: RAVService, Reason: Operation not allowed as appliance has ongoing RAV Migrations. java.lang.RuntimeException: Interconnect Service Workflow deleteServiceMesh failed. Error: Unable to proceed. Appliance Name: <Service_Mesh_Name>-IX-I1, Blocking Service: RAVService, Reason: Operation not allowed as appliance has ongoing RAV Migrations. at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.getSubflowJobDataArray(AbstractInterconnectJob.java:758) at com.vmware.vchs.hybridity.service.interconnect.AbstractInterconnectJob.checkComplete(AbstractInterconnectJob.java:2308) at com.vmware.vchs.hybridity.service.interconnect.InitiateServiceMeshOperation.handleState(InitiateServiceMeshOperation.java:170) 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)
VMware HCX 4.11.x
This error typically occurs when previously completed or failed migrations leave 'stale' entries in the HCX database, causing the system to believe those migrations are still active.
Should you encounter this issue, open a Support Request with Broadcom and supply the following:
HCX Version: The exact version currently running.
HCX Support Bundles: Bundles from both the source and target environments. Please ensure these include the Database dump and the logs for the affected Service Mesh.
Handling Log Bundles for offline review with Broadcom support.
Collecting Logs and Database Dumps for Ongoing or Intermittent Issues in HCX
Uploading files to cases on the Broadcom Support Portal
Creating and managing Broadcom cases
For more information, review the Broadcom HCX TechDoc and Knowledge Base articles linked below:
Clearing the Migration History
Canceling an HCX Migration using APIs
Manual removal of an HCX Service Mesh and Compute Profile