vmware-stsd service fails to start and PNID domain is duplicated when changing PNID in vCenter Server Management Interface
search cancel

vmware-stsd service fails to start and PNID domain is duplicated when changing PNID in vCenter Server Management Interface

book

Article ID: 421598

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The PNID is the Primary Network Identifier.

The upgrade from vCenter Server 7.x to 8.x fails because the PNID and the vCenter Server hostname do not match.

When changing the PNID in the vCenter Server Management Interface (VAMI), the vmware-stsd service fails to start, and the PNID domain is duplicated after the change.

Example: If you change the PNID from example to example.vmware.com, the PNID changes to example.vmware.com.vmware.com.

Environment

VMware vCenter Server 7.x

Cause

This issue occurs due to the following conditions:

  • vCenter Server on Windows was installed with a short name instead of an FQDN.
  • The LocalOS Identity Source for the vCenter Server Appliance is set to a short name instead of `localos`.
  • The PNID is registered with a short name.
  • You are attempting to change the PNID from a short name to an FQDN.

Resolution

This issue is caused by multiple issues.
Before performing the workaround below, please create an appropriate backup/snapshot of your vCenter Server.

Delete the LocalOS ID registered with the short name of the vCenter Server and register it with the ID [localos].

  1. Log in to the vCenter Server with administrator privileges using the vSphere Client.
  2. From the home menu, select [Administration].
  3. Select [Configuration] under [Single Sign-On].
  4. Select [Identity Sources] under the [Identity Provider] tab.
  5. Delete the LocalOS ID with the short name of the vCenter Server.
    1. Select the ID whose domain is the short name of the vCenter Server.
    2. Select [REMOVE] to delete the ID.
  6. Recreate the LocalOS ID.
    1. Select [ADD].
    2. Select [Local operating system of SSO server] as the identity source type.
    3. Enter [localos] as the name and select [ADD].

After completing the above steps, change the PNID.

  1. Change the DNS record to a temporary FQDN.
    e.g., appliance.vmware.com
  2. Change the PNID to the temporary FQDN, referring to Reconfigure the Primary Network Identifier.
    1. Log in to the vCenter Server Management Interface as the root user.
    2. Select [Networking] from the menu.
    3. Select [EDIT].
    4. Change the Hostname to the temporary FQDN.
    5. Select the confirmation checkbox and select [FINISH].
  3. Reboot the vCenter Server.
  4. Change the DNS record to the desired FQDN.
  5. Change the PNID to the desired FQDN.    
    1. Log in to the vCenter Server Management Interface as the `root` user.
    2. Select [Networking] from the menu.
    3. Select [EDIT].
    4. Change the Hostname to the desired FQDN.
    5. Select the confirmation checkbox and select [FINISH].
  6. Resolve old certificate issues using `lsdoctor`.
    Refer to KB 320837 for instructions on how to use `lsdoctor`.
  7. Reboot the vCenter Server.

Additional Information

Reconfigure the Primary Network Identifie

Update of PNID via Appliance Management Interface (VAMI) returns error: "Failed to to start STS service"

Changing PNID from short name to FQDN fails with an error "Failed to reset machine account"

Using the 'lsdoctor' Tool

vCenter Server 管理インターフェイスで PNID を変更すると vmware-stsd サービスが起動せず、PNID のドメインが重複する