VxRail bundle is available for an upgrade even though NSX-T upgrade is in-progress on VCF on VxRail 4.x environment
search cancel

VxRail bundle is available for an upgrade even though NSX-T upgrade is in-progress on VCF on VxRail 4.x environment

book

Article ID: 312131

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

This is to inform the customers/end users that it is a known issue and you would need to progress with the usual upgrade path i.e. NSX-T upgrade -> VC upgrade -> VxRail upgrade unless otherwise mentioned for a particular release.

Symptoms:
After SDDC Manager is upgraded and the necessary BoM upgrade bundles are uploaded to the environment, following may be observed:

1. VxRail bundles may become available for upgrade in SDDC manager UI Bundles page even before upgrading NSX-T and VC.

2. VxRail bundle is shown as available for upgrade in SDDC Manager UI Bundles page and Update/Patches tab even though BoM upgrade is still in-progress on VCF on VxRail 4.X environment.

Note: If VxRail upgrade is triggered before NSX-T and VC are upgraded, either the VxRail upgrade would fail or the environment would be in unsupported/unstable state due to incorrect compatibility between the BoM components.

Environment

VMware Cloud Foundation 4.4
VMware Cloud Foundation 4.3
VMware Cloud Foundation 4.2

Cause

The reason for this is Software Compatibility Sets file having additional compatibility set entries which are necessary for other upgrade paths, specifically for Async patching of BoM components.

Resolution

Follow the below steps: 
Complete NSX-T upgrade, VC upgrade and then trigger the upgrade for VxRail unless otherwise mentioned for the particular release.

Workaround:
No workaround available