I was working on some test configuration in my lab and noticed the update pop-up. So just checked it out on my vCenter Server 7.0 update planner for more details about this patch.
Out of curiosity, checked the release notes for the same in order to understand details about this patch since it is marked as critical.
VMware has recently released patch for vCenter Server 7.0, dated 19 May 20 Build 16189094. This update fixes vSAN issues. In vCenter Server 7.0 systems, if vSphere Lifecycle Manager is enabled on a vSAN cluster, vSAN File Services cannot be enabled on the same cluster and vice versa.
“vSphere Lifecycle Manager and vSAN File Services cannot be simultaneously enabled on a vSAN cluster“
Updating your vCenter server to vCenter Server 7.0.0a Build number 16189094 ensures that the vSAN File Services and vSphere Lifecycle Manager are interoperable. You can enable both services at the same time in the vSAN Cluster.
You can download this patch by going to the VMware Patch Download Center.
To Install the patch:
- Attach the
VMware-vCenter-Server-Appliance-188.8.131.5200-16189094-patch-FP.isofile to the vCSA.
- Log in to the appliance shell as a user as root and run the following commands:
- To stage the ISO:
software-packages stage --iso
- To see the staged content:
software-packages list --staged
- To install the staged rpms:
software-packages install --staged
- To stage the ISO:
Planning Upgrade to vCenter Server 7.0.0a from 6.5 or 6.7?
There are few limitations related to upgrade from previous versions of vSphere. Upgrade to vCenter Server 7.0.0a is not supported from below listed versions of vSphere.
- vCenter Server 6.5.0 U3j – 16275158*
- vCenter Server 6.7.0 U3g – 16046470
- vCenter Server 6.7.0 U3h – 16275304*
This is to avoid the code regression which happens in back-in-time upgrade scenarios. That sounds little odd right? 🙂 Let’s understand what it means.
Assume that your current installation is vSphere 6.5 u2d which released on 29-Nov-2018. Now you are planning to upgrade it to vSphere 6.7u1 which released on 16-Oct-2018. So, vSphere 6.7u1 is therefore considered a back-in-time release with reference to vSphere 6.5u2d.
A back-in-time scenario is defined as an upgrade path that would result in the deliberate regression of code and security fixes.
Below are the upgrade matrix from vSphere 6.5 and 6.7 to vSphere 7.0.0a
vCenter Server 6.5 to 7.0 upgrade matrix:
|vCenter Release – Build Number||7.0.0 – 15952498||7.0.0a – 16189094|
|12/19/2019||6.5.0 U3f – 15259038||Yes||Yes|
|1/30/2020||6.5.0 U3g – 15505374*||Yes||Yes|
|2/27/2020||6.5.0 U3h – 15679215*||Yes||Yes|
|3/26/2020||6.5.0 U3i – 15808842*||Yes||Yes|
|5/28/2020||6.5.0 U3j – 16275158*||No||No|
vCenter Server 6.7 to 7.0 upgrade matrix:
|vCenter Server – Build Numbers||7.0-15952498||7.0.0a-16189094|
|12/05/2019||6.7.0 U3b – 15132721||Yes||Yes|
|01/30/2020||6.7.0 U3c – 15505668*||Yes||Yes|
|02/27/2020||6.7.0 U3d – 15679281*||Yes||Yes|
|03/26/2020||6.7.0 U3e – 15808844*||Yes||Yes|
|04/09/2020||6.7.0 U3f – 15976714||No||Yes|
|04/28/2020||6.7.0 U3g – 16046470||No||No|
|05/28/2020||6.7.0 U3h – 16275304*||No||No|
I hope it’s helpful. Have fun upgrading.
!!! Cheers !!!