VMware Cloud Community
unixadmin1907
Contributor
Contributor

Cannot apply latest patch via esxcli for ESXi 7

I am trying to update my esxi 7 standalone host from 7.0 Update 3 to ESXi 7.0 Update 3i. My ESXi 7 is installed on a USB 32GB.

esxcli software sources profile list -d /vmfs/volumes/CamStorage/VMwar
e-ESXi-7.0U3i-20842708-depot.zip
Name Vendor Acceptance Level Creation Time Modification Time
------------------------------ ------------ ---------------- ------------------- -----------------
ESXi-7.0U3si-20841705-standard VMware, Inc. PartnerSupported 2022-12-08T00:00:00 2022-12-08T00:00:00
ESXi-7.0U3si-20841705-no-tools VMware, Inc. PartnerSupported 2022-12-08T00:00:00 2022-11-24T01:25:32
ESXi-7.0U3i-20842708-standard VMware, Inc. PartnerSupported 2022-12-08T00:00:00 2022-12-08T00:00:00
ESXi-7.0U3i-20842708-no-tools VMware, Inc. PartnerSupported 2022-12-08T00:00:00 2022-11-24T05:06:48

 

esxcli software profile update -d /vmfs/volumes/CamStorage/VMware-ESXi
-7.0U3i-20842708-depot.zip -p ESXi-7.0U3si-20841705-standard
[StatelessError]
The transaction is not supported: VIB VMware_bootbank_vsan_7.0.3-0.60.20841705 cannot be live installed. VIB VMW_bootbank_nvmetcp_1.0.0.1-1vmw.703.0.35.19482537 cannot be live installed. VIB VMware_bootbank_cpu-microcode_7.0.3-0.60.20841705 cannot be live installed. VIB VMW_bootbank_irdman_1.3.1.22-1vmw.703.0.50.20036589 cannot be live installed. VIB VMware_bootbank_native-misc-drivers_7.0.3-0.60.20841705 cannot be live installed. VIB VMW_bootbank_bnxtnet_216.0.50.0-44vmw.703.0.50.20036589 cannot be live installed. VIB VMW_bootbank_lpfc_14.0.169.26-5vmw.703.0.50.20036589 cannot be live installed. VIB VMW_bootbank_bnxtroce_216.0.58.0-23vmw.703.0.50.20036589 cannot be live installed. VIB VMware_bootbank_gc_7.0.3-0.60.20841705 cannot be live installed. VIB VMware_bootbank_esx-update_7.0.3-0.60.20841705 cannot be live installed. VIB VMW_bootbank_ne1000_0.9.0-1vmw.703.0.50.20036589 cannot be live installed. VIB VMW_bootbank_vmkusb_0.1-7vmw.703.0.50.20036589 cannot be live installed. VIB VMW_bootbank_icen_1.4.1.20-1vmw.703.0.50.20036589 cannot be live installed. VIB VMW_bootbank_iser_1.1.0.1-1vmw.703.0.50.20036589 cannot be live installed. VIB VMware_bootbank_lsuv2-lsiv2-drivers-plugin_1.0.0-12vmw.703.0.50.20036589 cannot be live installed. VIB VMware_bootbank_esx-base_7.0.3-0.60.20841705 cannot be live installed. VIB VMW_bootbank_iser_1.1.0.1-1vmw.703.0.20.19193900 cannot be removed live. VIB VMware_bootbank_lsuv2-lsiv2-drivers-plugin_1.0.0-9vmw.703.0.20.19193900 cannot be removed live. VIB VMW_bootbank_irdman_1.3.1.20-1vmw.703.0.20.19193900 cannot be removed live. VIB VMware_bootbank_esx-dvfilter-generic-fastpath_7.0.3-0.20.19193900 cannot be removed live. VIB VMware_bootbank_vsan_7.0.3-0.20.19193900 cannot be removed live. VIB VMware_bootbank_cpu-microcode_7.0.3-0.20.19193900 cannot be removed live. VIB VMW_bootbank_lpfc_14.0.169.25-5vmw.703.0.20.19193900 cannot be removed live. VIB VMW_bootbank_bnxtnet_216.0.50.0-41vmw.703.0.20.19193900 cannot be removed live. VIB VMW_bootbank_nvmetcp_1.0.0.0-1vmw.703.0.20.19193900 cannot be removed live. VIB VMware_bootbank_gc_7.0.3-0.20.19193900 cannot be removed live. VIB VMware_bootbank_native-misc-drivers_7.0.3-0.20.19193900 cannot be removed live. VIB VMW_bootbank_icen_1.4.1.7-1vmw.703.0.20.19193900 cannot be removed live. VIB VMW_bootbank_ne1000_0.8.4-11vmw.703.0.20.19193900 cannot be removed live. VIB VMware_bootbank_esx-update_7.0.3-0.20.19193900 cannot be removed live. VIB VMware_bootbank_esx-base_7.0.3-0.20.19193900 cannot be removed live. VIB VMW_bootbank_bnxtroce_216.0.58.0-23vmw.703.0.20.19193900 cannot be removed live. VIB VMW_bootbank_vmkusb_0.1-6vmw.703.0.20.19193900 cannot be removed live.
Please refer to the log file for more details.

Reply
0 Kudos
4 Replies
a_p_
Leadership
Leadership

Not 100% sure whether it's related, but did you enter the security profile "ESXi-7.0U3si-20841705-standard" rather than the default profile by purpose?

André

Reply
0 Kudos
mohitpanot
Contributor
Contributor

Can you confirm, if your system is booted from the USB as you mentioned.

Looks like your system is booted from memory (and hence treated like a stateless host), and hence the operation you are performing (profile update) becomes invalid on a stateless host.

You can execute 'vmkfstools -Ph /bootbank' on the host, if it says "ramdisk" in the output, then your host is not booted from the ramdisk.

Then then debugging should go in the direction, why your host booted from  memory (and not from the USB which you mentioned).

Reply
0 Kudos
unixadmin1907
Contributor
Contributor

vmkfstools -Ph /bootbank
visorfs-1.00 (Raw Major Version: 0) file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 3.7 GB, 2.9 GB available, file block size 4 KB, max supported file size 0 bytes
Disk Block Size: 4096/4096/0
UUID: 00000000-00000000-0000-000000000000
Partitions spanned (on "notDCS"):
ramdisk:tmp
Is Native Snapshot Capable: NO

Reply
0 Kudos
unixadmin1907
Contributor
Contributor

The fix was to reinstall ESXi and reconfigure everything from scratch. I am not sure what happened, but something funky was going on.

Reply
0 Kudos