Script to remove stale service registrations from vCenter Server.

Products

• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

Improper decommissioning of the 6.x PSC node or any vCenter from ELM might leave stale service registrations on the vCenter which leads to other issues.

Steps to check stale registrations on vCenter Server:

1. List the services registered within the Platform Services Controller from the vCenter SSH session.
   

   • /usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert > /tmp/psc.txt

2. Validate the number of service registrations for each vCenter:

   • less /tmp/psc.txt | grep -i "Service Type: " | sort | uniq -c

   • For an environment with two vCenters in Enhanced Linked Mode (ELM), there would be two service registrations for each service. If there are more than two, then these can be potentially stale ones.
     
     
3. Identify a valid registration against stale registration using /etc/vmware/install-defaults/vmdir.ldu-guid to compare Node ID from above file (/tmp/psc.txt):
   • For Example:
     • The below service registration belongs to the mentioned Node ID.

               Name: ServiceName
               Description: ServiceDescription
               Service Product: com.vmware.cis
               Service Type: ServiceType
               Service ID: 1f10##8f-438d-##b-90f8-47e7d6##a94f
               Site ID: default-first-site
               Node ID: b2b7##1e-5##9-4a55-88##-699f##eb1d6f
               Owner ID: [email protected]
               Version: 1.0
               Endpoints:
                       Type: com.vmware.cis.data.provider
                       Protocol: vmomi
                       URL: https://VC_PNID:443/sdk
                       SSL trust: 
                       Endpoint Attributes:
                               cis.common.ep.localurl: http://localhost:11080/sdk
               Attributes:
                       com.vmware.cis.cm.HostId: 603b3##1-f##b-4##2-a##5-81517##8f47a

   • The Node ID should match the entry in /etc/vmware/install-defaults/vmdir.ldu-guid.

Environment

• VMware vCenter Server 7.x
• VMware vCenter Server 8.x

Cause

Improper decommissioning of external PSC or vCenter in Enhanced Linked Mode (ELM).

Resolution

• Follow the below steps to remove the stale service registrations from vCenter Server using the service_unregister_stalenode.sh script.

  1. 1. Shut down all the vCenter nodes in ELM and take a powered-off snapshot from each vCenter VM.
     2. Power on all the vCenters.
     3. Log in to any one of the vCenter's SSH session.
     4. Validate the incorrect node by checking the URL from the service registration output.
     5. Note down the Node ID for the incorrect service registration.
     6. Run the attached script attached to this KB.
        • Steps to run the script:
          • ./service_unregister_stalenode.sh <Node_ID of stale node>
            • Example: ./service_unregister_stalenode.sh b2b7##1e-5##9-4a55-88##-699f##eb1d6f
          • You will be prompted for the username/password.
            • The username would be administrator@<sso-domain>, by default it's [email protected]
     7. Resolve “bad interpreter” Error (If Encountered)
        • If running the script returns:

          bash: ./service_unregister_stalenode.sh: /bin/bash^M: bad interpreter: No such file or directory

          Run the command

          sed -i -e 's/\r$//' service_unregister_stalenode.sh

     8. Validate the stale service registrations have been removed successfully.
     9. If stale service registrations cannot be removed, try the ldapdelete method per Removing stale lookupservice service registrations from vmdir using ldapdelete on vCenter Server

         

Additional Information

Note: This script will not remove service registrations that do not have node IDs; example: sso:groupcheck, sso:admin.

• These services can be unregistered using jXplorer or by following the steps mentioned in Error: "Could not connect to one or more vCenter Server Systems" in the vSphere Client
  
  
• Refer the following KB for manual method to remove stale service registrations from vCenter Server:
  • Remove stale entries by manual method