/common/logs/admin/app.log2025-11-27 12:54:25.461 UTC [InterconnectService_SvcThread-587, Ent: HybridityAdmin, , TxId: ####-####-####-9aae918858da] ERROR c.v.v.h.a.postgresdb.PostgresAdapter- Error executing query ERROR: duplicate key value violates unique constraint "HbrToHostConnectionAlerts_applianceId_1_hostId_1_vCenterId_1"
Detail: Key ((val ->> 'applianceId'::text), (val ->> 'hostId'::text), (val ->> 'vCenterId'::text))=(####-####-####-8f8e6ddfa19a, <IX-IP>, ) already exists.or
2026-05-01 07:59:07.503 UTC [InterconnectService_SvcThread-82, J:c4045155, , TxId: ########-####-####-####-d9cf825bf310] ERROR c.v.v.h.s.i.InitiateApplianceOperation- InterconnectRedeploy workflow failed with error Redeploy of Interconnect Appliance failed. Interconnect Service Workflow InterconnectRedeploy failed.
Error: Deploy and Configuration of Interconnect Appliances Failed. Interconnect Service Workflow DeployAppliance failed. Error: Unknown.VMware HCX
This is failing due to some stale entries for the appliance in HCX DB.
If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.
Please collect HCX Logs [Select All] and upload to SR. Refer Gather Technical Support Logs
WORKAROUND:
If no migrations are currently in progress, you may deploy a new Service Mesh instance with the same service appliance type. Please ensure that the new appliance selects an IP address different from the one referenced in the error log.
If the appliance is a Network Extender you can remove the affected instance by reducing the number of NEs in the Service Mesh configuration: this will clean up the stale records and then allow increasing their number back to the original value in the Service Mesh, deploying a new replacement NE in the current version of HCX.