This week, a problem took me two day to find a solution and nothing found on the web to this special case. The final fix was mistake, which solved the whole problem. But, what happens?
I started to create a new VMware ESXi cluster with vSAN, vLCM and NSX. If you ever did it, specially NSX with vLCM, you know that you have to create the cluster in legacy mode, install NSX at first and switch to vLCM at the end. The first steps worked great, the cluster is up and running, NSX is installed on every node. Now I switched from Update Manager to the new Lifecycle Manager. Import the Image, checked the component and vendor plugins, all right. Start to remediate and BAMMM: Failure!
Error Message
A general system error occurred:
Failed to validate the checksum of VIB '/tmp/offlineBundleMSMSmJ/vib20/nsx-vdpi/VMware_bootbank_nsx-vdpi_4.0.1.1.0-8.0.20598730.vib', because the computed checksum differs from the expected one stored in metadata. Make sure the specified VIB is NOT corrupted and the expected checksum stored in metadata is correct. OK, reboot ESXi, retry, nothing. Some error. I downloaded the module from Broadcom portal, upload to the ESXi and installed via command line. Reboot the server. The vLCM still want to reinstall the NSX packages, with same version. WHY?
In the end, I checked the sha256 sum of the VIB on the vCenter Server and NSX repository and see, they really differs. I downloaded the VIB from NSX and copy it to the vCenter, restart the update manager server. Same problem. I moved back to the original VIB, and now I did the mistake, I chose the wrong service to restart and this impacted all other vCenter Services to stop. After safe restart of all services, it worked!!! The simple solution to fix the checksum error was to restart the vCenter Services.
In Germany, we say „Reboot tut gut“ it means like „reboot will fix most issues“. And this was already the solution to this error. Two days, one reboot 🤦