"Error while fetching server configuration entity" under CSE Management in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• When navigating to VCD Provider Portal > More > Kubernetes Container Cluster > CSE Management > Server Details, the portal fails with the following error message:

  Error while fetching server configuration entity

  

• Checking the service status on the Container Service Extension (CSE) server via "systemctl status cse" shows the service is Loaded but stuck in the Activating state.

• Reviewing /root/cse.log on the CSE server reveals the following authentication panic:

  goroutine 1 [running]:
main.main()
          /app/main.go:61 +0x1cbe
I0814 06:07:33.960242 28680 main.go:55] Connecting to [https://vcd.example.com] as [system:cse-server]
I0814 06:07:33.960274 28680 auth.go:52] Using VCD OpenAPI version [36.0]
E0814 06:07:34.782780 28680 auth.go:66] failed to authenticate using refresh token
panic: error logging into VCD: [unable to get swagger client from secrets: [unable to get bearer token from secrets: [failed to set authorization header: [error finding LoginUrl: could not find valid version for login: API version 36.0 is not supported: version = 36.0 is not supported]]]]
•  

Environment

VMware Cloud Director 10.6.x

Container Service Extension 4.2.1

Cause

VMware Cloud Director 10.6.x removes support for legacy OpenAPI versions, including API version 36.0. Container Service Extension (CSE) 4.2.1 relies on API v36.0 for authentication calls, creating an API version mismatch that prevents the CSE daemon from initializing.

Resolution

• Refer to the Broadcom Product Interoperability Matrix to confirm the supported upgrade path for your target VMware Cloud Director version.
• Upgrade the Container Service Extension appliance and UI plugin to version 4.2.2 or later, which supports VCD 10.6.x API versions.