ESXi Host Upgrade Precheck Fails in SDDC Manager with error "The Host is Incompatible with the Patch/Upgrade ISO File"
Article ID: 405966
Updated On:
Products
Issue/Introduction
The ESXi host upgrade precheck in SDDC Manager fails with the following error,
Description
Upgrade - ESX_HOST ######
Progress Messages
The host ########-####-####-####-############ is incompatible with the Patch/upgrade iso file
Error:
Message: ########-####-####-####-############ is incompatible with the Patch/upgrade iso file
Remediation Message: High: Incompatible patch or upgrade files. Please verify that the patch file is compatible for host. Refer LCM and VUM log file. Check /var/log/vmware/vcf/lcm. Please retry the upgrade once the upgrade is available again.
Reference Token: ######
In the /var/log/vmware/vcf/lcm/lcm.log on the SDDC Manager we see such error,
"upgradeStatus":"COMPLETED_WITH_FAILURE","upgradeError":{"errorType":"NONRECOVERABLE","stage":"ESX_UPGRADE_VUM_STAGE_SCAN_HOST","errorCode":"ESX_UPGRADE_VUM_HOST_INCOMPATIBLE","errorDescription":"The host ########-####-####-####-############ is incompatible with the Patch/upgrade iso file","errorDescriptionCodes":["ESX_UPGRADE_VUM_HOST_INCOMPATIBLE"],"errorDescriptionAttributes":{"0":"########-####-####-####-############"},"metadata":"\nCheck for errors in the lcm log files located on SDDC Manager under /var/log/vmware/vcf/lcm.\n Please retry the upgrade once the upgrade is available again."
In the /var/log/vua.log file (or vua-1, vua-2.log....) on the ESXi host, we observed this WARNING of TPM_VERSION and ERROR of PACKAGE_COMPLIANCE, (the ######## refers to the target ESXi version specified for the upgrade)
--> <test>
--> <name>TPM_VERSION</name>
--> <expected>
--> <value>True</value>
--> </expected>
--> <found>
--> <value>False</value>
--> </found>
--> <result>WARNING</result>
--> </test>
.......
.......
--> <test>
--> <name>PACKAGE_COMPLIANCE</name>
--> <expected>
-->
--> </expected>
--> <found>
--> <value>VMware_bootbank_esx-base_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_gc_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_gc-esxio_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio-dvfilter-generic-fastpath_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_bmcal_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_vsan_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_clusterstore_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_trx_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio-update_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esx-update_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio-base_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_vcls-pod-crx_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_vsanhealth_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_bmcal-esxio_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_native-misc-drivers_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio-combiner_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_crx_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esx-dvfilter-generic-fastpath_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_infravisor_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_vds-vsip_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_loadesx_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esxio-combiner-esxio_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_vdfs_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_drivervm-gpu-base_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_native-misc-drivers-esxio_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_cpu-microcode_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_esx-xserver_8.0.3-0.73.########</value>
--> <value>VMware_bootbank_loadesxio_8.0.3-0.73.########</value>
--> </found>
--> <result>ERROR</result>
--> </test>
While the log does indicate an issue, it does not explicitly state which component is causing the incompatibility.
Environment
SDDC 5.x
ESXi 7.x/8.x managed by SDDC.
Cause
In the log file /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-*.log we see the actual reason for the upgrade failure is "com.vmware.vcIntegrity.HostUpgrade.UnsupportedTPMVersion",
YYYY-MM-DDTHH:MM:SS+0000 info vmware-vum-server[######] [Originator@#### sub=HostUpgradeScanner] [scannerImpl ###] Precheck script test result: 'ERROR', test 'PACKAGE_COMPLIANCE', expected '', found 'VMware_bootbank_clusterstore_8.0.3-0.73.######## VMware_bootbank_loadesx_8.0.3-0.73.######## VMware_bootbank_bmcal-esxio_8.0.3-0.73.######## VMware_bootbank_esxio-dvfilter-generic-fastpath_8.0.3-0.73.######## VMware_bootbank_gc_8.0.3-0.73.######## VMware_bootbank_drivervm-gpu-base_8.0.3-0.73.######## VMware_bootbank_crx_8.0.3-0.73.######## VMware_bootbank_bmcal_8.0.3-0.73.######## VMware_bootbank_trx_8.0.3-0.73.######## VMware_bootbank_esx-xserver_8.0.3-0.73.######## VMware_bootbank_esx-update_8.0.3-0.73.######## VMware_bootbank_vdfs_8.0.3-0.73.######## VMware_bootbank_esx-base_8.0.3-0.73.######## VMware_bootbank_esxio-base_8.0.3-0.73.######## VMware_bootbank_esxio_8.0.3-0.73.######## VMware_bootbank_loadesxio_8.0.3-0.73.######## VMware_bootbank_vds-vsip_8.0.3-0.73.######## VMware_bootbank_esxio-combiner-esxio_8.0.3-0.73.######## VMware_bootbank_esxio-update_8.0.3-0.73.######## VMware_bootbank_native-misc-drivers_8.0.3-0.73.######## VMware_bootbank_esx-dvfilter-generic-fastpath_8.0.3-0.73.######## VMware_bootbank_vcls-pod-crx_8.0.3-0.73.######## VMware_bootbank_cpu-microcode_8.0.3-0.73.######## VMware_bootbank_vsan_8.0.3-0.73.######## VMware_bootbank_native-misc-drivers-esxio_8.0.3-0.73.######## VMware_bootbank_esxio-combiner_8.0.3-0.73.######## VMware_bootbank_gc-esxio_8.0.3-0.73.######## VMware_bootbank_vsanhealth_8.0.3-0.73.######## VMware_bootbank_infravisor_8.0.3-0.73.########' and errortype is 18
YYYY-MM-DDTHH:MM:SS+0000 info vmware-vum-server[######] [Originator@#### sub=HostUpgradeScanner] [scannerImpl ###] (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "com.vmware.vcIntegrity.HostUpgrade.UnsupportedTPMVersion",
--> arg = <unset>,
--> message = <unset>
--> }
--> ]
Resolution
The root cause of the upgrade failure appears to be the absence of a TPM (Trusted Platform Module) on the host.
To further investigate and confirm the TPM status, we suggest the following:
1. Check TPM status in vCenter
In the vCenter vSphere Client, go to vCenter > Monitor > Security, where you can view the TPM status for all connected hosts. Verify whether the affected host shows a TPM device.
2. Check BIOS/UEFI settings on the host
Ensure that TPM is enabled in the system BIOS or UEFI settings. Sometimes, TPM may be present but disabled at the firmware level.
3. Verify TPM hardware health
If TPM is enabled in BIOS but still not detected in vCenter, it's possible the TPM chip may be faulty or not functioning properly. It is recommended to contact the hardware vendor for further diagnosis or replacement.
Feedback
