Errors: "Failed to fetch Kubernetes clusters" when browsing the Kubernetes cluster
search cancel

Errors: "Failed to fetch Kubernetes clusters" when browsing the Kubernetes cluster

book

Article ID: 385637

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • When browsing the Kubernetes cluster list from VMware Cloud Director UI in Kubernetes Container Clusters, the Kubernetes cluster list on the first page is available while there is an error when browsing the Kubernetes clusters on the second page as per screenshot below:
  • On the API call when browsing the Kubernetes clusters you see below entry in the response:

     

    API call:

    GET https://cloud.example.com/cloudapi/1.0.0/entities/interfaces/vmware/k8s/1.0.0?sortAsc=name&filter=entityType==urn%3Avcloud%3Atype%3Acse%3AnativeCluster%3A2.1.0,entityType==urn%3Avcloud%3Atype%3Acse%3AnativeCluster%3A2.0.0,entityType==urn%3Avcloud%3Atype%3Acse%3AnativeCluster%3A1.0.0,entityType==urn%3Avcloud%3Atype%3Avmware%3Atkgcluster%3A1.0.0,((entityType==urn%3Avcloud%3Atype%3Avmware%3AcapvcdCluster%3A1.1.0,entityType==urn%3Avcloud%3Atype%3Avmware%3AcapvcdCluster%3A1.3.0))&page=2&pageSize=10

    Response:

        "minorErrorCode": "VCD_50070",
        "message": "Invalid multisite cursor specified. Restart the query at page 1.",
        "stackTrace": "com.vmware.vcloud.multisite.exceptions.MultisiteQueryArgumentsException: Invalid multisite cursor specified. Restart the query at page 1.\n\tat com.vmware.vcloud.multisite.query.QueryExecutor$AbstractExecutor.<init>(QueryExecutor.java:224)\n\tat com.vmware.vcloud.multisite.query.OpenApiQueryExecutor$JsonQueryExecutor.<init>(OpenApiQueryExecutor.java:114)\n\tat com.vmware.vcloud.multisite.query.OpenApiQueryExecutor.executeQuery(OpenApiQueryExecutor.java:88)\n\tat
    [...]
  • More that 10 Kubernetes clusters have been deployed.

Environment

VMware Cloud Director 10.5
VMware Cloud Director Container Service Extension 4.2.1
VMware Cloud Director Container Service Extension UI Plugin 4.2.1

Cause

This is a known issue when More that 10 Kubernetes clusters have been deployed and browsing the Kubernetes clusters on the second page.

Resolution

The issue is under review by engineering.

Subscribe to this knowledge article to get updates on this issue.

Workaround: none