"Unable to find VUM extension registered with VC" error while registering Update Manager with vCenter Server Appliance

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Similar entries can be observed while registering Update Manager with VCSA by running these commands:
  
  root@vcsa [ ~ ]# /usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc
  YYYY-MM-DDTHH:MM:SSZ Getting value for install-parameter: cm.url
  Unable to find VUM extension registered with VC
   
• Unable to start the Update Manager Services. Similar log entries can be seen in /var/log/vmware/vmware-updatemgr/updatemgr-utility.log file, while trying to start the Update Manager service.

updatemgr-utility.log
[YYYY-MM-DD HH:MM:SSZ INFO] Adding VUM options in DB
[YYYY-MM-DD HH:MM:SSZ INFO] Added VUM options in Database.
[YYYY-MM-DD HH:MM:SSZ INFO] Successfully updated VUM extension with VC
[YYYY-MM-DD HH:MM:SSZ INFO] Install Key store for Jetty
[YYYY-MM-DD HH:MM:SSZ INFO] Keystore installed successfully.
[YYYY-MM-DD HH:MM:SSZ ERROR] Unable to find VUM extension registered with VC

vmware-vum-server-log4cpp.log
[YYYY-MM-DD HH:MM:SSZ 'JobDispatcher' 139826955921152 INFO]  [JobDispatcher, 86] Creating instance of JobDi
spatcher
[YYYY-MM-DD HH:MM:SSZ 'JobDispatcher' 139826955921152 INFO]  [JobDispatcher, 129] JobDispatcher construct
[YYYY-MM-DD HH:MM:SSZ 'Activation' 139826955921152 ERROR]  [activationValidator, 244] sysimage.fault.SSLCertificateError
[YYYY-MM-DD HH:MM:SSZ 'Activation' 139826955921152 ERROR]  [activationValidator, 252] No started
[YYYY-MM-DD HH:MM:SSZ 'Activation' 139826955921152 INFO]  [activationValidator, 257] Leave Validate. Failed

Environment

VMware vSphere Update Manager 6.7.x
VMware vSphere Update Manager 6.5.x
VMware vSphere Update Manager 6.0.x

Cause

The issue occurs if the Update manager extension is missing from the vCenter server.

 

To verify this, go to https://<VC_IP>/mob/?moid=ExtensionManager> and validate that the "com.vmware.vcIntegrity" extension is missing.

Resolution

To resolve the issue, register the Update Manager extension "com.vmware.vcIntegrity" manually and then re-register the Update manager to VCSA:

1. Access vCenter Server Mob through browser using URL https://<VC_IP/FQDN>/mob/?moid=ExtensionManager
2. From methods, select RegisterExtension
3. Copy and Paste the below XML string and click on invoke method. This should return void and when we go back to link in step 1, "com.vmware.vcIntegrity" should appear under Extensions.
   
   XML:
   
   <extension>
   <description>
   <label>VMware Update Manager</label>
   <summary>VMware Update Manager</summary>
   </description>
   <key>com.vmware.vcIntegrity</key>
   <version>REPLACE_ME</version>
   <lastHeartbeatTime>YYYY-MM-DDTHH:MM:SSZ</lastHeartbeatTime>
   </extension>
   
   Note: Check the <version> in /etc/vmware/service-state/updatemgr/extension.xml file and update it in the XML before you invoke the method. Check the <lastHeartbeatTime> using the date command, formatting using the example above.
    
4. Refresh the VUM service by running the command:
   
   /usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
   For 6.7: /usr/lib/vmware-updatemgr/bin/refreshCerts-utility.py
5. Re-register the update manager back to VC using the utility vmware-vciInstallUtils
   
   Syntax : /usr/lib/vmware-updatemgr/bin/vmware-vciInstallUtils -C /usr/lib/vmware-updatemgr/bin/ -L /var/log/vmware/vmware-updatemgr/ -I /usr/lib/vmware-updatemgr/bin/ -v <vCenter Server FQDN> -p 80 -U <SSO Administrator Account> -P '<Password>' -S /usr/lib/vmware-updatemgr/bin/extension.xml -O extupdate
   
   Example : /usr/lib/vmware-updatemgr/bin/vmware-vciInstallUtils -C /usr/lib/vmware-updatemgr/bin/ -L /var/log/vmware/vmware-updatemgr/ -I /usr/lib/vmware-updatemgr/bin/ -v vcsa.domain.local -p 80 -U [email protected] -P '<Password>' -S /usr/lib/vmware-updatemgr/bin/extension.xml -O extupdate
6. Ensure the vci-integrity.xml file ownership is with updatemgr user:

chown updatemgr:updatemgr /usr/lib/vmware-updatemgr/bin/vci-integrity.xml

     7. Restart VUM service by running the command:

service-control --start vmware-updatemgr