OPERATIONAL DEFECT DATABASE
...
...
When you register Update Manager with VCSA by running these commands, you see entries similar to: root@vcsa [ ~ ]# /usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc 2017-08-04T18:28:52.588Z Getting value for install-parameter: cm.url Unable to find VUM extension registered with VC Unable to start the Update Manager Services. You will find the similar log entries when you try to start the Update Manager service in /var/log/vmware/vmware-updatemgr/updatemgr-utility.log file updatemgr-utility.log [2020-03-30 15:03:11,633 INFO] Adding VUM options in DB [2020-03-30 15:03:11,935 INFO] Added VUM options in Database. [2020-03-30 15:03:11,935 INFO] Successfully updated VUM extension with VC [2020-03-30 16:21:19,769 INFO] Install Key store for Jetty [2020-03-30 16:21:20,973 INFO] Keystore installed successfully. [2020-03-30 16:21:21,336 ERROR] Unable to find VUM extension registered with VCvmware-vum-server-log4cpp.log [2020-03-30 15:10:17:883 'JobDispatcher' 139826955921152 INFO] [JobDispatcher, 86] Creating instance of JobDi spatcher [2020-03-30 15:10:17:883 'JobDispatcher' 139826955921152 INFO] [JobDispatcher, 129] JobDispatcher construct [2020-03-30 15:12:22:666 'Activation' 139826955921152 ERROR] [activationValidator, 244] sysimage.fault.SSLCertificateError [2020-03-30 15:12:22:666 'Activation' 139826955921152 ERROR] [activationValidator, 252] No started [2020-03-30 15:12:22:666 'Activation' 139826955921152 INFO] [activationValidator, 257] Leave Validate. Failed
The issue occurs if the Update manager extension is missing from the vCenter server. To verify go to https://<VC_IP>/mob/?moid=ExtensionManager> and "com.vmware.vcIntegrity" extension will be missing.
To resolve the issue, register the Update Manager extension "com.vmware.vcIntegrity" manually and then re-register the Update manager to VCSA: Access vCenter Server Mob through browser using URL https://<VC_IP/FQDN>/mob/?moid=ExtensionManagerFrom methods, select RegisterExtensionCopy 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>2021-08-03T11:41:06</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. 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.pyRe-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 vcsa65-a.vmwaretest.local -p 80 -U administrator@vsphere.local -P 'VMware123!' -S /usr/lib/vmware-updatemgr/bin/extension.xml -O extupdate Ensure the vci-integrity.xml file ownership is with updatemgr user: chown updatemgr:updatemgr /usr/lib/vmware-updatemgr/bin/vci-integrity.xml Restart VUM service by running the command: service-control --start vmware-updatemgr
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
