Domain repoint for embedded vCenter Server fails with error: "domain_consolidator Failed to set machine id"
search cancel

Domain repoint for embedded vCenter Server fails with error: "domain_consolidator Failed to set machine id"

book

Article ID: 338163

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Domain repoint for embedded vCenter fails.
  • In the /var/log/vmware/cloudvm/domain_consolidator.log file, you see entries similar to:
<YYYY-DD-MM>T<TIME> INFO domain_consolidator Setting LduGuid
<YYYY-DD-MM>T<TIME> INFO domain_consolidator vmdir registry updated with the original LDU_GUID
<YYYY-DD-MM>T<TIME> INFO domain_consolidator RC = 25
Stderr = Error 5: Authorization failed.
Verify account has proper administrative privileges.
2019-07-05T17:19:27.962Z ERROR domain_consolidator Failed to set machine id,Exception:{
    "detail": [
        {
            "args": [
                "Stderr: Error 5: Authorization failed.\nVerify account has proper administrative privileges.\n"
            ],
            "localized": "An error occurred while invoking external command : 'Stderr: Error 5: Authorization failed.\nVerify account has proper administrative privileges.\n'",
            "translatable": "An error occurred while invoking external command : '%(0)s'",
            "id": "install.ciscommon.command.errinvoke"
        }
    ],
    "componentKey": null,
    "resolution": null,
    "problemId": null
}
<YYYY-DD-MM>T<TIME> INFO domain_consolidator Failed
<YYYY-DD-MM>T<TIME> ERROR domain_consolidator Failed to Re-install PSC services
<YYYY-DD-MM>T<TIME> INFO domain_consolidator Embedded Domain Repoint Service Command Phase Failed. Please check logs
<YYYY-DD-MM>T<TIME> INFO domain_consolidator Failed executing <cis.service_data.DcServicesCommand object at 0x7f3874b8d4e0>
<YYYY-DD-MM>T<TIME> ERROR domain_consolidator Re-pointing operation has failed during execution mode.
<YYYY-DD-MM>T<TIME> INFO domain_consolidator Repoint failed. Restore from backup

 
  • The hostname shown in /etc/hosts and when using the hostname -f command do not match the  FQDN that is configured for the PNID of the vCenter.
For example:
root@vcsa1 [ ~ ]# hostname -f;
vcsa1.subdomain.mydomain.com

root@vcsa1 [ ~ ]# /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost;
vcsa1.mydomain.com


Environment

VMware vCenter Server Appliance 6.7.x

Cause

This issue is caused by a mismatch between the FQDN that was configured as the PNID during the vCenter Server deployment and the hostname that is currently configured.

Resolution

To resolve the issue, follow the steps below:
  1. Connect to the source vCenter via SSH.
  2. Find the current PNID using the command below:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost;
  1. Run the command below to enter the network configuration:
/opt/vmware/share/vami/vami_config_net;
  1. Select option 3, Hostname and enter the FQDN returned from step 2.
  2. Select option 1 to exit the network configuration.
  3. Reboot the vCenter Server using the command below:
reboot -f;

Note: Rebooting the vCenter Server will make it temporarily unavailable for use.