Supervisor upgrade gives error in pre-check: "The Supervisor version <version name> is interoperable with the current infrastructure in degraded mode. Please refer to the Supervisor upgrade documentation"
search cancel

Supervisor upgrade gives error in pre-check: "The Supervisor version <version name> is interoperable with the current infrastructure in degraded mode. Please refer to the Supervisor upgrade documentation"

book

Article ID: 421455

calendar_today

Updated On:

Products

VMware vSphere Kubernetes Service

Issue/Introduction

  • Supervisor upgrade gives error in pre-check:
    "The Supervisor version <version name> is interoperable with the current infrastructure in degraded mode. Please refer to the Supervisor upgrade documentation to fetch the list of degraded features.
    '<Supervisor-name>' can be updated from version <version-name> to version <version-name>. You can monitor the configuration progress from the Supervisors tab."

  • From the DCLI "com vmware vcenter namespacemanagement software clusters get --cluster domain-c#" the Supervisor cluster shows 'Ready' and does show the available versions for Supervisor upgrade.

  • We get an error while listing the Content Library from DCLI:
    dcli> com vmware vcenter namespacemanagement lifecycle content libraries list
    libraries:
       - library:
            id: ########-####-####-####-############
         status: ERROR

  • From VCDB of the vCenter we have below entry for the Content Library:
    • Enter into the VCDB of the vCenter:
      /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres
    • Check the status of the content library:
      VCDB=> select * from supervisor_content_source_configs;
      id | library | status | state | phase | messages | create_timestamp | last_update_timestamp ----+--------------------------------------+--------+-------+-------+------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------+------------------+----------------------- 1 | ########-####-####-####-############ | ERROR | APPLY | ERROR | [{"Message": {"Id": "vcenter.wcp.content.library.processing.error", "Args": ["########-####-####-####-############", "malformed Supervisor OVF template name <template-name>"], "Params": null, "Localized": null, "DefaultMessage": "Err or processing Content Library ########-####-####-####-############, Error: malformed Supervisor OVF template name <template-name>." }, "Severity": "ERROR"}] | 1763555259 | 1764591440 (1 row)
  • The logs in /var/log/vmware/wcp/wcpsvc.log report the below entries:

    YYYY-MM-DD <Time> error wcp [content/validate.go:69] [libraryID=########-####-####-####-############ opID=cl-########-####-####-####-############] Supervisor item name ob-24536965-photon-5-amd64-v1.31.4---vmware.1-fips-vkr.3 should start with prefix supervisor-#####.

    YYYY-MM-DD <Time> error wcp [content/controller.go:543] [libraryID=########-####-####-####-############ opID=cl-########-####-####-####-############] pre ovf download check failed, err: malformed Supervisor OVF template name ob-24536965-photon-5-amd64-v1.31.4---vmware.1-fips-vkr.3

    YYYY-MM-DD <Time> error wcp [content/controller.go:187] [opID=svContentWorker-########-####-####-####-############] Error reconciling Content Library ########-####-####-####-############, err: <nil>

  • The Content Library in use is local Content Library.

Environment

vSphere Supervisor Releases

Cause

Starting with VCF 9.0, vSphere Supervisor Kubernetes releases are delivered separately from vCenter. To enable or upgrade the Supervisor, you must create a subscribed content library that synchronizes with VMware's content delivery network, allowing access to the required Supervisor release images.

Resolution

To resolve the issue, create a subscribed content library using the official VMware repository URL for asynchronous releases. This new library must then replace the existing local content library to successfully synchronize and access the required Supervisor images for platform updates.
Refer Configure a Subscribed Content Library for Supervisor Images.