Issues with Upgrading vLCM Clusters Involving HSM/HSP from vLCM Configure Upgrade UI

Products

• VMware SDDC Manager

Issue/Introduction

During the upgrade process of vLCM, when submitting or finalizing upgrades for cluster images that include HSP/HSM details, users may encounter a validation error pertaining to the HSP/HSM specification on the review page of the vLCM wizard UI.

Purpose: This notice aims to proactively alert customers about this potential issue to reduce the number of new support requests they might submit.

GUI error in text format - for ease of use/ findability 
 
"Invalid Package/Version com.vmware.hardwaresupport/3.0.0-0. It is not configured on the vCenter."
or
"Invalid Package/Version com.<VENDOR_REFERENCE>.hsm/<VERSION_TBD>. It is not configured on the vCenter"

Log example output - lcm.log

[DATE && TIME] ERROR [vcf_lcm,7e9f4dca4f9f4bec,ea46] [c.v.v.l.r.a.c.v.u.UpgradeController,http-nio-127.0.0.1-7400-exec-9] Scheduling Upgrade Failed
com.vmware.evo.sddc.lcm.model.error.LcmException: Invalid Package/Version com.<TBD>.hsm/<TBD>. It is not configured on the vCenter
or 
[DATE && TIME] ERROR [vcf_lcm,75gfrsyjebf3443c,ab96] [c.v.v.l.r.a.c.v.u.UpgradeController,http-nio-127.0.0.1-7400-exec-9] Scheduling Upgrade Failed
com.vmware.evo.sddc.lcm.model.error.LcmException: Invalid Package/Version com.vmware.hardwaresupport/3.0.0-0. It is not configured on the vCenter


Environment

VCF 5.X

Cause

The issue arises because the user interface is sending incorrect HSP details to the API, which leads to a failure in initiating the upgrade due to ongoing validation errors.

Resolution

This problem will be resolved in future releases.

Workaround:

In cases where HSM/HSP is involved, initiate the upgrade through the API. 

Example:

API Endpoint: https://<sddc-manager-fqdn>/v1/upgrades'

Payload:

{
    "bundleId": "<bundleId>",
    "resourceType": "CLUSTER",
    "parallelUpgrade": true,
    "resourceUpgradeSpecs": [
        {
            "resourceId": "<clusterId>",
            "upgradeNow": false,
            "enableQuickboot": true,
            "evacuateOfflineVms": true,
            "esxUpgradeOptionsSpec": {
                "enableQuickPatch": false
            },
            "personalitySpec": {
                "personalityId": "<personalityId>"
            }
        }
    ],
    "draftMode": true
}

Note: if there are multiple cluster, additional are resourceUpgradeSpecs required.