When I upgraded one of my vCenter 6.7 to vCenter 7.0, I got a strange error on Lifecycle Manager. The error was; a status 404 vCenter compliance.
Somehow the VMware Update Manager DB from the previous vCenter did not migrate properly to the new vCenter 7.0 Lifecycle Manager. We need to erase the Lifecycle Manager so that the service can start correctly.
We need to stop the service and run the command to erase the DB.
Note: Before you start this process, for the safe side, create a snapshot of your vCenter.
Also, be beware that this process will clean all custom Baselines that you may have in your vCenter / Update Manager.
Connect to vCenter shell and run the following commands.
service-control --stop vmware-updatemgr
rm -rf /storage/updatemgr/patch-store/*
service-control --start vmware-updatemgr
After this, your Lifecycle Manager will start downloading all patches again, and all will be working. So you should wait some minutes before using it.
All is working, and Lifecycle Manager is back with all the patches and ESXi versions.
I hope vCenter 6.7 upgrade 7.0 Lifecycle Manager not starting helps you fix your vCenters after an upgrade (this can also happen when upgrading from 6.6 to 6.7).
Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.