Hi Neo Chen,
I will be frank and say it should make no functional difference which option you go for - if for instance the patch is for a required security vulnerability then it isn't going to be (potentially) so helpful if not all hosts have the required patch applied if one/some still have this vulnerability or some other issue that the patch addresses.
From a functional perspective (e.g. just considering basic ESXi+vSAN components) it doesn't make much difference if the hosts are running on different builds of ESXi 8.0 U3 (unless of course there is a major/impactful fix for either of those components in the later build).
Is there a valid reason that in the year of 2025 that the end-customer has a VM that needs to be pinned to a specific host? You should look into ways of addressing that limitation so that you can properly use the flexibility of vSAN without being hindered.
Original Message:
Sent: Jan 09, 2025 02:34 AM
From: Neo Chen
Subject: About VSAN OSA upgrade situation
Hi All,
I have 4 HPE VSAN Ready Nodes on my end, and they are running OSA on an ESXi8.0u3 environment.
Recently, I need to update the HPE firmware and ESXi patch to the latest version.
Just because the customer has a VM tied to one host, it cannot be shut down temporarily. May I ask:
1. It is recommended to first upgrade the other three hosts and wait until the remaining one can be restarted before upgrading?
2. Or will still wait for the time when we can restart everything at once and upgrade everything together?
Because I am not sure if there will be any issues with VSA if there are other firmware and version differences after the upgrade.