I played some musical chairs with licenses to get a successful upgrade off on these, but odd that even with a manual vib install off a full repo – I still get that error. Seems to be some corruption that happened with a previous upgrade, as I do notice the host profile version was stuck as stating an old 6.7 that we haven't used in quite some time. Not sure, but a fix without vCenter would be nice for someone that is also facing this.
Original Message:
Sent: 5/23/2024 8:12:00 AM
From: Martin Timmons
Subject: RE: Upgrade VIB(s) "loadesx" is required for the transaction.-- Can't upgrade 7.0.3 to recent build
The OP clearly states that this is a standalone ESXi host - so not connected to a vcenter.
Original Message:
Sent: May 17, 2024 12:26 AM
From: Louis Dang
Subject: Upgrade VIB(s) "loadesx" is required for the transaction.-- Can't upgrade 7.0.3 to recent build
You can use vCenter to the update. It will help you solve the problem.
Original Message:
Sent: May 15, 2024 04:04 PM
From: ANDREW BROCKERHOFF
Subject: Upgrade VIB(s) "loadesx" is required for the transaction.-- Can't upgrade 7.0.3 to recent build
[root@esxi:~] esxcli software sources profile list --depot=/vmfs/volumes/
61d4599d-9bd52ea1-288a-0050568f5f83/VMware-ESXi-7.0U3p-23307199-depot.zip
Name Vendor Acceptance Level Creation Time Modification Time
----------------------------- ------------ ---------------- ------------------- -----------------
ESXi-7.0U3p-23307199-standard VMware, Inc. PartnerSupported 2024-03-05T00:00:00 2024-03-05T00:00:00
ESXi-7.0U3p-23307199-no-tools VMware, Inc. PartnerSupported 2024-03-05T00:00:00 2024-02-14T13:03:18
[root@esxi:~] esxcli software profile update \
> -p ESXi-7.0U3p-23307199-standard \
> -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-in
dex.xml
[InstallationError]
Upgrade VIB(s) "loadesx" is required for the transaction. Please use a depot with a complete set of ESXi VIBs.
Please refer to the log file for more details.
[root@esxi-01-v11:~]
We've tried to manually install the loadesx vib as well, but same error. Has anyone faced this issue when trying to upgrade a stand-alone ESXi host running vSphere 7 std?