Enhanced Linked Mode Creation Failed at "Starting Tagging Data import" Step
search cancel

Enhanced Linked Mode Creation Failed at "Starting Tagging Data import" Step

book

Article ID: 374641

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When creating Enhanced Linked Mode (ELM) between vCenter Servers using the cmsso-util domain-repoint -m execute command, the process fails during the "Starting Tagging Data import" step.



  • The pre-check using cmsso-util domain-repoint -m pre-check reports no issues.

  • /var/log/vmware/cloudvm/cmsso_util.log contains the following error:

    YYYY-MM-DD HH:MM:SS INFO cmsso_util Failed to execute script /usr/lib/repoint/taggingservice_component_script.py
YYYY-MM-DD HH:MM:SS INFO cmsso_util Failed executing <cis.component_data.DcImportCommand object at 0x############>
YYYY-MM-DD HH:MM:SS ERROR cmsso_util Re-pointing operation has failed during execution mode.
YYYY-MM-DD HH:MM:SS INFO cmsso_util Repoint failed. Restore from backup
  • When reviewing /var/log/vmware/cloudvm/domain_data_export.log you find errors like in the example below:
    YYYY-MM-DD HH:MM:SS [main [] ERROR com.vmware.vim.dataservices.ImportTaggingData opId=]- ExecutionException :(dataservice.fault.AlreadyExistsFault) { faultCause = null, faultMessage = null }
YYYY-MM-DD HH:MM:SS [main [] ERROR com.vmware.vim.dataservices.ImportTaggingData opId=]- Failure importing Tagging info, local msg: (dataservice.fault.AlreadyExistsFault) { faultCause = null, faultMessage = null }
YYYY-MM-DD HH:MM:SS [main [] ERROR com.vmware.vim.dataservices.ImportTaggingData opId=]- Exception importing tagging data : java.util.concurrent.ExecutionException: (dataservice.fault.AlreadyExistsFault) { faultCause = null, faultMessage = null }
YYYY-MM-DD HH:MM:SS [main [] ERROR com.vmware.vim.dataservices.ImportTaggingData opId=]- Stack trace : java.util.concurrent.ExecutionException: (dataservice.fault.AlreadyExistsFault) { faultCause = null, faultMessage = null }
  • In /var/log/vmware/vpxd-svcs/vpxd-svcs.log you see below mentioned error
    YYYY-MM-DD HH:MM:SS [dataservice-0 [] ERROR com.vmware.cis.core.tagging.internal.impl.CategoryManagerImpl opId=7550ef6d-####-####-####-##########IS] Category with name Backup already exists:
YYYY-MM-DD HH:MM:SS [dataservice-0 [] ERROR com.vmware.cis.core.tagging.vmodl.MoTagManager opId=7550ef6d-####-####-####-##########IS] Failed to create category with name : Backup com.vmware.cis.core.tagging.exception.AlreadyExistsException: Category with name Backup already exists:

Environment

VMware vCenter Server 7.0.x

VMware vCenter Server 8.0.x

Cause

The issue occurs when a tag category exists in both vCenter Servers, that has the same name but different case spelling. For example:

  • vCenter 1: Category named "Backup"
  • vCenter 2: Category named "backup"

During ELM creation, vCenter attempts to import tagging categories from one vCenter to the other. Due to the case-insensitive nature of category and tag names, the creation process detects a naming conflict and fails, preventing the ELM creation from completing.

Resolution

To resolve this issue, ensure that offline snapshots exist for all of the vCenter Servers, then update the category name in one of the vCenters to match the other exactly, including letter case, by taking the steps below:

  1. Log in to the vSphere Client (HTML5 UI) of the vCenter where the name mismatch exists.

  2. Navigate to Menu > Tags & Custom Attributes > Categories.

  3. Locate the conflicting category name (e.g., backup).

  4. Click on the category name to open its details.

  5. Click the Edit (pencil) icon.

  6. In the Name field, change the category name to match the one on the other vCenter exactly (e.g., rename backup to Backup).

  7. Click Save to apply the changes.

  8. Re-run the cmsso-util domain-repoint -m execute command to continue ELM creation. If this fails, please restore snapshot of ALL linked vCenter instances before the domain repoint was ran.

Once the names match exactly, vCenter will recognize the categories as the same and skip trying to recreate them, allowing the ELM creation to complete successfully.

 

Additional Information

Important Considerations When Renaming Categories:

  • Impact Analysis: Before renaming a category, understand its usage. Renaming a category might affect existing tags and any automation that relies on the category name.

  • Consistency: Aim for consistent category naming across your vCenter environment for better management and clarity.
Powered by Wolken Software