Some vCenter tags are missing post HCX migration
search cancel

Some vCenter tags are missing post HCX migration

book

Article ID: 422713

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • After migration we see that VM's are missing some of the assigned tags.
  • Before migration the VMs have 4 tags.
  • After migration we see that VM's are missing some of these tags.

 

The following entries are found in /common/logs/admin/app.log:

2025-11-18 08:45:24.498 UTC [VmotionService_SvcThread-134778, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] INFO  c.v.v.h.migration.common.VmUtil- Created tag under category '<Name>': name - '########-####-####-####-############', description - <description>, Id - 'null'
2025-11-18 09:10:57.643 UTC [VmotionService_SvcThread-134919, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] INFO  c.v.v.h.migration.common.VmUtil- Created tag under category '<Name>': name - '########-####-####-####-############', description - '<description>', Id - 'null'
2025-11-18 09:47:33.948 UTC [VmotionService_SvcThread-135128, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] INFO  c.v.v.h.migration.common.VmUtil- Created tag under category '<Name>': name - '########-####-####-####-############', description - '<description>', Id - 'null'

2025-11-18 08:45:24.498 UTC [VmotionService_SvcThread-134778, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] WARN  c.v.v.h.a.vapi.TagOperationsFacet- Tag ########-####-####-####-############ already Exists
2025-11-18 09:10:57.643 UTC [VmotionService_SvcThread-134919, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] WARN  c.v.v.h.a.vapi.TagOperationsFacet- Tag ########-####-####-####-############ already Exists
2025-11-18 09:47:33.948 UTC [VmotionService_SvcThread-135128, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] WARN  c.v.v.h.a.vapi.TagOperationsFacet- Tag ########-####-####-####-############ already Exists

Environment

VMware HCX

Cause

The vCenter is not case sensitive, but HCX has this gap where it's doing case sensitive check on the tag names and deducing that the relevant tag is missing on target and trying to create a new one. But vCenter flags the error that the tag already exists.

Resolution

This is a known issue impacting VMware HCX and this will be resolved in future releases.