how upgrade to ESXI 7.0.3

[loungehostmaste]

now that vCenter upgrade no longer kills it's network configuration (https://communities.vmware.com/t5/VMware-vCenter-Discussions/VC-7-0u2c-breaks-network-config/m-p/286... i thought i go the iso-way for the two hosts to make sure HPE specific drivers are updated too

upgrade with HPE Custom ISO fails, see attachment

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

they way i upgraded ESXi with patches from http://www.vmware.com/patch/download/ for 10 years now fails too

[root@esx2:~] esxcli software vib update --depot=/vmfs/volumes/nfs/updates/VMware-ESXi-7.0U3-18644231-depot.zip
[InstallationError]
This upgrade transaction would skip ESXi Base Image VIB(s) VMW_bootbank_nvmetcp_1.0.0.0-1vmw.703.0.0.18644231, VMware_bootbank_bmcal_7.0.3-0.0.18644231, VMware_bootbank_esxio-combiner_7.0.3-0.0.18644231, VMware_bootbank_trx_7.0.3-0.0.18644231, 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 upgrade.
Please refer to the log file for more details.

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

maybe god knows how to use image profiles - i don't and i shouldn't need to for a simple task like an OS upgrade

[root@esx2:~] esxcli software profile update --profile=local --depot=/vmfs/volumes/nfs/updates/VMware-ESXi-7.0U3-18644231-depot.zip
[NoMatchError]
No image profile found with name 'local'
id = local
Please refer to the log file for more details.

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

oh, and connection to lifecycle-manager also only god knows how it works and why it should be needed to keep a simple infsratructure with two hosts up-to-date fails with authentication error

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

are you guys kidding me?
why can't ESXi just seek, download and install it's updates out from it#s webinterface without handholding to begin with?

[subdriven]

I'm in exactly the same boat and totally agree with you. It is ridiculous this is the upgrade process.

[loungehostmaste]

there is a newer HPE ISO with a different checksum but the same nonsense - VMware becomes laughable.....

[loungehostmaste]

this is all a joke!

* that you need to seek the profile name is a joke
* the hardware warning is a joke
* that 4 GB RAM with no running guest isn't enough is a joke
* and yes *this* is a nested ESXi running FOUR GUESTS fine for years

[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates] esxcli software profile update --profile=ESXi-7.0U3a-18825058-standard --depot=/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates/VMware-ESXi-7.0U3a-18825058-depot.zip
[HardwareError]
Hardware precheck of profile ESXi-7.0U3a-18825058-standard failed with warnings: <CPU_SUPPORT WARNING: The CPU in this host may not be supported in future ESXi releases. Please plan accordingly.>

Apply --no-hardware-warning option to ignore the warnings and proceed with the transaction.
Please refer to the log file for more details.

[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates] esxcli software profile update --no-hardware-warning --profile=ESXi-7.0U3a-18825058-standard --depot=/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates/VMware-ESXi-7.0U3a-18825058-depot.zip
[InstallationError]
Failed to create ramdisk vibdownload: Errors:
No space left on device
     cause = (146, 'Cannot reserve 146 MB of memory for ramdisk vibdownload')
Please refer to the log file for more details.

[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680/updates] df -h
Filesystem   Size   Used Available Use% Mounted on
VMFS-6      45.0G   7.7G     37.3G  17% /vmfs/volumes/storage
VFFS         3.8G   1.7G      2.1G  45% /vmfs/volumes/OSDATA-5e8df93c-83c5d849-717f-000c29f07680
vfat       499.7M 200.7M    299.0M  40% /vmfs/volumes/BOOTBANK1
vfat       499.7M 195.8M    304.0M  39% /vmfs/volumes/BOOTBANK2

[GaelV]

Hi, if you have VM with RDM disks be very careful, the 7.0.3 fails any vMotion with RDM disks (i'm in that case since this morning)

=> https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-updat...

[loungehostmaste]

thanks god we have only two identical hosts and a direct-SAS storage - and that's why all the issues since 2018 and the bloating of vcenter and anything makes me that terrible angry - with the resources VCSA in 2021 needs i started with a single standalone ESXi in 2008 hosting *everything* and back in the days VMware just worked (ok we had luck that the we shutdown everything because it's a expired beta even if it isn't was found and solved shortly before we started)

[KGundermann]

I'm now sitting 5 hours at my pc, trying to upgrade our ESXi host to 7.03.

Downloaded 10G ISO file with latest Smart Update Manager (SUM) 2021.10.0

SUM updated some components (ILO, ROM Flash Firmware..) but fails at the last two:
- Integrated Smart Update Tools 2.9.0
- HPE Agent Management Bundle Smart Component
looking at the logs: it fails cause its still in ESXI 7.0.0.

So I downloaded another 6 GB ISO : ESXi 7.0 U3 Upgrade Pack v1.4.3
Added it to SUM, run Inventory again, still nothing to see from U3 !

So how the heck what is the procedure to update to 7.0.3 ??

[loungehostmaste]

didn't you realize that 7.0.3 to 7.0.3U3b are no longer available because VMware realized they are crap? at least here the 7.0.3 U3b is running for 26 days so i won't downgrade - no 7.x did here run that long before things starting to fall into pieces

[KGundermann]

NO, I didn't knew that, thank your for your advise,

so I will give U2 a try ..

[loungehostmaste]

https://customerconnect.vmware.com/en/downloads/info/slug/datacenter_cloud_infrastructure/vmware_vsp...

red alert on top:
Critical Alert - ESXi 7.0 U3, U3a, U3b and vCenter 7.0 U3b are no longer available for download due to critical issues

https://kb.vmware.com/s/article/86398