esxupdate: 3701199: imageprofile: INFO: Adding VIB VMware_bootbank_vmware-hbr-agent_<build and version> to ImageProfile (Updated) <Current image profile of the ESXi Host>
esxupdate: 3701199: esxupdate: ERROR: An esxupdate error exception was caught:
esxupdate: 3701199: esxupdate: ERROR: Traceback (most recent call last):
esxupdate: 3701199: esxupdate: ERROR: File "/usr/sbin/esxupdate", line 222, in main
esxupdate: 3701199: esxupdate: ERROR: cmd.Run()
esxupdate: 3701199: esxupdate: ERROR: File "/lib64/python3.8/site-packages/vmware/esx5update/Cmdline.py", line 153, in Run
esxupdate: 3701199: esxupdate: ERROR: File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 851, in InstallVibsFromSources
esxupdate: 3701199: esxupdate: ERROR: inst, removed, exitstate = self._installVibs(curprofile,
esxupdate: 3701199: esxupdate: ERROR: File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 1097, in _installVibs
esxupdate: 3701199: esxupdate: ERROR: exitstate = self._validateAndInstallProfile(
esxupdate: 3701199: esxupdate: ERROR: File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 1256, in _validateAndInstallProfileVMware vSphere ESXi
VMware vCenter Server
vSphere Replication Appliance
Site Recovery Manager
The version of the hbr-agent VIB isn't compatible with the image profile of the ESXi Host. This is because even though the Host shows up on version "n" the underlying image profile isn't updated and therefore is on an "n-1" version. To check and confirm the same, run the below set of commands
esxcli system version get
esxcli --server=<server_name> software profile get
In the ideal circumstances, the version details should be the same for both the commands.
The affected ESXi Host needs to be updated/upgraded with the correct image profile. Refer the following Broadcom doc on the same- https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/how-to-upgrade-hosts-by-using-esxcli-commands-upgrade/upgrade-or-update-a-host-with-image-profiles-upgrade.html
A major difference in the version of the Host and its image profile is mostly due to the ESXi upgrade/update being carried out using the "esxcli software vib" commands. Starting with ESXi 8.0 Update 2, upgrading or updating ESXi using the commands "esxcli software vib update" or "esxcli software vib install" is no longer supported. Refer the following kb article on this- https://knowledge.broadcom.com/external/article/343840/patching-esxi-host-using-command-line.html