SDDC manager UI shows inconsistency in the "Upgrade Options" when performing upgrades of vLCM images based ESXi hosts clusters

Products

• VMware SDDC Manager

Issue/Introduction

The Initiation of vLCM image-based ESXi cluster upgrades goes through two stages, with each having its own UI wizard. 

• • Configure Update
  • Schedule Update 

• At the 4th step of the Configure Update, the Users will have to provide inputs for Upgrade Options, by selecting/unselecting the check box of the following options: Sequential clusters Upgrade, Enable Quick Boot, Enforce live Patch, Migrate Powered off and suspended VMs. 
• At the 5th step of the configure upgrade, a review page will be shown with the details inputs provided, as shown below. 

• When finished, a precheck is initiated automatically, and the Cluster is now available to start the upgrade, with the scheduled upgrade button available. 
• When Schedule Update is clicked, it will be seen at the review page that all the Upgrade Options 'Sequential clusters Upgrade, Enable Quick Boot, Enforce live Patch, Migrate Powered off and suspended VMs' are seen as disabled, even though they might have been enabled at the Configure Update wizard. Refer to the image below: 

• From the /var/log/vmware/vcf/lcm-debug.log It can be seen that the upgrade spec was set as per the options set in the Configure Upgrade section: 

YYYY-MM-DDT00:00:00.000+0000 DEBUG [vcf_lcm,959905b49b8f4226,f49f] [c.v.v.l.r.a.c.v.u.UpgradeDissemblers,http-nio-127.0.0.1-7400-exec-7] resourceUpgradeSpec is ResourceUpgradeSpec(resourceId=5######-8###-4###-a###-e###########, shutdownVms=null, toVersion=null, scheduledTimestamp=null, upgradeNow=false, personalitySpec=PersonalitySpec(personalityId=1#######-3###-4###-9################, hardwareSupportSpecs=null), customIsoSpec=null, enableQuickboot=true, evacuateOfflineVms=true, esxUpgradeOptionsSpec=EsxUpgradeOptionsSpec(esxUpgradeFailureAction=null, enforceHclValidation=null, enableQuickPatch=false), hostsToUpgrade=null)

 

Environment

VCF 5.2.0.0

Cause

This is a cosmetic issue in VCF 5.2.0.0 

Resolution

No functional impact will be seen, and the upgrade will go through based on the inputs set at "Configure Update". 

The issue has been resolved in VCF 5.2.1.x and above.