This is an informational article, this is a known issue.
Symptoms:
After performing skip level upgrade to VCF 4.3.0.0 / 4.3.1 from 4.1.x or 4.2.x, one or more of the following symptoms is observed:
- vRealize bundles do not show up as available for upgrade
- Bundles of previous versions for product components (NSX-T / VC/ ESXi) show up as available for upgrad
- /var/log/vmware/vcf/lcm/lcm-debug.log shows the below message
2021-06-03T14:44:29.250+0000 WARN [vcf_lcm,60319965ff2c4524,435c] [c.v.e.s.l.s.UpgradeServiceHelper,pool-7-thread-5] NSX-T cluster with ID: vip-nsxt-mgmt.vcf.local, name: vip-nsxt-mgmt.vcf.local, version: {"version":"3.1.2.0.0.17883596"} is partially upgraded
2021-06-03T14:44:29.251+0000 WARN [vcf_lcm,60319965ff2c4524,435c] [c.v.e.s.l.s.i.SkipUpgradeServiceImpl,pool-7-thread-5] Skipping aliasing to VCF version 4.3.0.0 since there are partial NSX-T upgrade on the system
- Upgrade activity log in SDDC Manager UI for VCF upgrade will have message as follows:
Skipped enabling skip level upgrade to VCF version 4.3.0.0 since there are partial NSX-T upgrade on the system, please complete NSX-T upgrade first, then call API /v1/system/settings/version-aliases to enable skip level upgrade to the target VCF version