"esxcli software vib update --depot" broken

[loungehostmaste]

after https://communities.vmware.com/t5/VMware-vCenter-Discussions/VC-7-0u2c-breaks-network-config/m-p/2864229 you guys even broke a simple hypversior update in a nested ESXi - what about Vmware start doing their homework again instead break things left and right while make all the stuff more and more complex?

what is that difficult update a linux appliance and apply simple updates on a ESXi host?
the vCenter in the meantime needs 14 GB RAm for two host and 20 guests
friends as i started in 2008 the whole host had 16 GB RAM

and guess what: all the Fedora guests on-top are still the same installations from 2008 upgraded *online* from F9 to F34 and they even need less resources as back in these days - i wish i am not just 43 years old so that i can quit that braindead business i loved years ago

[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates] esxcli software vib update --depot=/vmfs/volumes/storage/updates/VMware-ESXi-7.0U2c-18426014-depot.zip
[InstallationError]
This upgrade transaction would skip ESXi Base Image VIB(s) VMW_bootbank_atlantic_1.0.3.0-8vmw.702.0.0.17867351, VMware_bootbank_clusterstore_7.0.2-0.20.18426014, which could
cause failures post upgrade. Please use an alternative upgrade method that would install the above VIB(s). For example, use an image profile instead of VIBs to perform the upg
rade.
Please refer to the log file for more details.

[a_p_]

According to the release notes (https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u2c-release-notes.html), you must use the esxcli software profile update command for updating/patching from the CLI.

André

[loungehostmaste]

and what should i enter as profile name?

[a_p_]

You can find out about the profiles that are provided in a bundle by either running e.g.

esxcli software sources profile list -d /vmfs/volumes/folder/bundle.zip

or from the release notes. Then append -p <profile-name> to the update command line.

André

[loungehostmaste]

seems to work but to be honest that's a technical poverty certificate 

well, let's see if it works on a machine installed with a custom HPE iso and currently you can't update from U2 to U3 that way while the last upgrade was 6.4 to 7.0.2 directly (https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/how-upgrade-to-ESXI-7-0-3/m-p/2870472#M6778)

-------------------------------

[root@esx2:~] esxcli software sources profile list -d /vmfs/volumes/nfs/updates/VMware-ESXi-7.0U3a-18825058-depot.zip
Name Vendor Acceptance Level Creation Time Modification Time
----------------------------- ------------ ---------------- ------------------- -----------------
ESXi-7.0U3a-18825058-standard VMware, Inc. PartnerSupported 2021-10-28T00:00:00 2021-10-28T00:00:00
ESXi-7.0U3a-18825058-no-tools VMware, Inc. PartnerSupported 2021-10-28T00:00:00 2021-10-25T07:08:49

-------------------------------

[root@esx2:~] esxcli software profile update --profile=ESXi-7.0U3a-18825058-no-tools --depot=/vmfs/volumes/nfs/updates/VMware-ESXi-7.0U3a-18825058-depot.zip
Update Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMW_bootbank_atlantic_1.0.3.0-8vmw.703.0.0.18644231,