Loading...
Loading...
The following errors might be encountered during installation or upgrades of ESXi hosts to 8.0: Update Manager compliance scans indicates that a baseline (creating used an imported ISO) is Incompatible and the error details indicate an error on the following lines: The following VIB(s) on the host or in the chosen baseline(s) do not have the required checksums on their payloads: {some VIB names} This will prevent VIB security verification and secure boot from functioning properly. Please remove these VIBs and check with your vendor for a replacement of these VIBs. While using esxcli software vib, profile or apply command to install VIB or upgrade the system, you see ProfileValidationError like: In ImageProfile (Updated) {Image Profile Name}, the payload(s) in VIB {some VIB name} does not have sha-256 gunzip checksum. This will prevent VIB security verification and secure boot from functioning properly. Please remove this VIB or please check with your vendor for a replacement of this VIB. Please refer to the log file for more details. While creating a ESXi server using an ISO image or while using the scripted installation, the following error is seen: <MISSING_GUNZIP_CHECKSUM_VIB_ERRORS: Found=[{some VIB names} Expected=[] These VIB(s) do not have the required sha-256 gunzip checksum for their payloads. This will prevent VIB security verification and secure boot from functioning properly. Please remove these VIBs and check with your vendor for a replacement of these VIBs.>
If there are VIBs present on ESXi that do not have the “sha-256” checksum-type and “gunzip” verify-process pair in the VIB metadata, an upgrade to ESXi 8.0 will fail, with a message identifying the VIBs that prevented the upgrade.
While the problematic VIBs are part of the host, the upgrade/installation cannot proceed. Thus, one of the following can be done: Please check with the vendors of the problematic VIBs if there are any updates available to the same. If available, please update these VIBs (using either a VUM baseline or using the esxcli commands) and retry the upgrade operation.If the problematic VIBs are not in use or no longer needed, remove them using esxcli command: “esxcli software vib remove –vibname <vibname1> –vibname <vibname2> –vibname <vibname3> …”and reattempt the upgrade operation. If the following VIBs are installed on the host, the required customer action (for upgrading to 8.0) is listed below:Vmware-perccli Dell has released newer version of perccli utility for ESXi 7.0 with different name “vmware-perccli64”.Customer needs to remove old VIB and install newer one before upgrading. Vmware-storcli Broadcom has released newer version of storcli for ESXi 7.0 with different name “vmware-storcli64”.Customer needs to remove old VIB and install newer one before upgrading. emulex-esx-elxmgmt Broadcom has newer version of this package for ESXi 7.0 with different name “Broadcom-ELX-esxcli-elxmmt”.Customer needs to remove old VIB and install newer one before upgrading. AvayaSome Avaya VIBs are not supported anymore, hence needs to be removed for upgrade, this includes: asavp-alarmingavaya-licensingavaya-hardenavaya-watchdavp-alarming New Avaya product offering uses esxcli software profile install -p $PROFILE (profile install) instead of (profile update) to remove previous VIBs and installs the new ones.Following VIBs are being developed with HEXDK version: vmware-esx-hexdk-devtools-7.0.0-1.0.15843807.x86_64, so new 7.0 version will be available: avaya-toolsavaya-easgwatchd-filesnative-cpldcplduser Dell sas-raid_boss-cli_6.x, SuperMicro TAS: Not supported on 8.0Remove VIB in order to upgrade to 8.0 NetAppNasPlugin 6.7 patch supports NetAppNasPlugin 1.1.2-3 which isn't supported for upgrade directly to 8.0. NetApp has newer version of this package from ESXi 7.x (NetAppNasPlugin.2.0-15.vib)Either approach is possible during upgrade to 8.01. Upgrade ESXi >=7.0.1 version followed by updating NetAppNasPlugin to 2.0-15 before 8.0 upgrade.2. Remove older NetAppNasPlugin vib before upgrade to ESXi8.0. Post upgrade, NetAppNasPlugin 2.0-15 vib can be installed. Note: The error in Lifecycle Manager might not contain the offending vibs, and instead show {precheckError}. In these cases, you can determine the problematic vibs from the /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log file: 2022-11-07T21:31:08.371Z info vmware-vum-server[07580] [Originator@6876 sub=HostUpgradeScanner] [scannerImpl 661] Precheck script test result: 'ERROR', test 'MISSING_GUNZIP_CHECKSUM_VIBS', expected '', found 'LSI_bootbank_vmware-perccli-007.0318.0000.0000_007.0318.0000.0000-01' and errortype is 422022-11-07T21:31:08.371Z info vmware-vum-server[07580] [Originator@6876 sub=HostUpgradeScanner] [scannerImpl 1749] (vmodl.LocalizableMessage) [--> (vmodl.LocalizableMessage) {--> key = "com.vmware.vcIntegrity.HostUpgrade.MissingGunzipChecksumVibs",--> arg = (vmodl.KeyAnyValue) [--> (vmodl.KeyAnyValue) {--> key = "found",--> value = "LSI_bootbank_vmware-perccli-007.0318.0000.0000_007.0318.0000.0000-01"--> }--> ],--> message = <unset>--> }--> ]
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.