Error "Unknown API version: 39.0.0-alpha" when deploying TKG cluster using CSE in VMware Cloud Director after upgrading to 10.6.1.1
search cancel

Error "Unknown API version: 39.0.0-alpha" when deploying TKG cluster using CSE in VMware Cloud Director after upgrading to 10.6.1.1

book

Article ID: 406971

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • After upgrading VMware Cloud Director (VCD) to version 10.6.1.1, deploying a Tanzu Kubernetes Grid (TKG) cluster using the Container Service Extension (CSE) fails with the following error:

    Unknown API version: 39.0.0-alpha

  • This issue occurs in a multisite VCD configuration where One site is upgraded to 10.6.1.1 and the other site remains on 10.5.x.
  • In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log the following error is seen:

    TIME | ERROR    | pool-jetty-55817          | DefaultExceptionMapper         | Internal server exception | requestId=###########-####-####-####-##############,request=GET https://
    VCD_FQDN/cloudapi/1.0.0/sessions/urn:vcloud:session:********-****-****-****-********d74f/accessib...,requestTime=###################,remoteAddress=###.###.###.###:15089,userAgent=Mozilla/5.0 (Windows NT 10.0
    ; Win64; x64) AppleWebKit/537.36 ...,accept=application/json;version 40.0.0-alpha
    java.lang.IllegalArgumentException: Unknown API version: 39.0.0-alpha
            at com.vmware.vcloud.api.rest.version.ApiVersion.fromValue(ApiVersion.java:534)
            at com.vmware.vcloud.api.rest.openapi.impl.auth.SessionsApiHandler.createAccessibleLocation(SessionsApiHandler.java:558)

Environment

VMware Cloud Director 10.6.1

VMware Cloud Director 10.6.1.1

CSE  4.2.2

Cause

In a multisite environment, the site running VCD 10.5.1 still uses API version 39.0.0-alpha. In VCD 10.6.1.1, this version was renamed to 39.0.0.

While the UI accessibility issues were addressed in 10.6.1.1, the SessionApiHandler component remains affected.

Resolution

The issue will been resolved in VCD version 10.6.1.2.

Workarounds:

OPTION 1
Revert Upgrade: Roll back to the previous working version of the software.

OPTION 2
Remove Multisite: Disconnect multisite functionality and operate as single, independent sites until both sites are upgraded to 10.6.1.1. For additional information, refer the documentation Configuring and Managing Multisite Deployments in Your VMware Cloud Director

OPTION 3 
Upgrade All Sites: Upgrade all sites in the multisite configuration to VCD 10.6.1.1 to ensure API version consistency.