Unable to list topics after upgrading from v1.3.0 to v1.4.2

[prasadkris]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

We have a Kafka UI deployment running inside our K8s cluster and it has been working like a charm. Yesterday we upgraded from version v1.3.0 to v1.4.2, and that update seems to have broken the setup, I’m unable to view the topic list for our clusters (other items like brokers, etc. still work fine). I just get a spinning wheel when I try to view the topic list. After reverting back to version v1.3.0, it started working fine again.

Expected behavior

The topic list should load correctly after the upgrade.

Your installation details

appVersion: v1.4.2
helm chart version: 1.5.3

helm values.yaml

image:
  registry: ghcr.io
  repository: kafbat/kafka-ui
  pullPolicy: IfNotPresent

yamlApplicationConfig:
  kafka:
    clusters:
      - name: xxxxxx
        bootstrapServers: kafka:9092
        schemaRegistry: http://avro-schema-registry:8081
        readOnly: false
      - name: xxxxxx
        bootstrapServers: xxxxxxx.svc.cluster.local:9092
      - name: xxxxxxxx
        bootstrapServers: xxxxxxxxxxx.svc.cluster.local:9092

  auth:
    type: OAUTH2
    oauth2:
      client:
        keycloak:
          clientId: kafka-ui
          clientSecret: xxxxxxxxxxxxxxxx
          scope: openid
          issuer-uri: xxxxxxxxxxxxxxxxxx
          user-name-attribute: preferred_username
          client-name: kafka-ui
          provider: keycloak
          custom-params:
           type: keycloak
  management:
    health:
      ldap:
        enabled: false
envs:
  config:
    LOGGING_LEVEL_IO_KAFBAT_UI: error
    LOGGING_LEVEL_ROOT: error

# Ingress configuration
ingress:
  enabled: true
  path: "/"
  pathType: "Prefix"  
  host: "kafka-ui.xxxxxxx.dev"
  tls:
    enabled: false

resources: {}

Steps to reproduce

1. Deploy kafka-ui version v1.3.0 on K8s and verify that the topic list loads correctly.
2. Upgrade kafka-ui from v1.3.0 to v1.4.2.
3. Open the kafka UI in the browser.
4. Go to Cluster → Topics for any configured cluster.
5. Observe that the topic list does not load and only a spinning loader is shown.

Screenshots

No response

Logs

No response

Additional context

No response

[github-actions]

Hi prasadkris! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[Haarolean]

Please share whatever there is in browser dev console

[prasadkris]

Thanks 🙏🏻 unfortunately I get nothing in the console, just a spinning wheel with no data in the dev console.

The debug logs captured during this issue are here if you’d like to have a look.

[germanosin]

@prasadkris could you please

1. share network tab queries and there results/body in the browser.
2. Try to query api directly /api/clusters/{clusterName}/topics
3. Check rbac and acl
4. Check error logs before queries (might be problem with metadata collection)

[prasadkris]

Thank you @germanosin! 🙏🏻 The topic list just goes into an endless spinning wheel, with no progress in the Network tab’s Queries section. The only issue is with the topics list; other details like info, broker list, etc. are displaying fine

I tried using a curl command to list the topics, but that also just hangs, whereas cluster info, cluster list, etc. are loading fine. Please find the logs at: https://gist.github.com/prasadkris/bbf90aaeaef2c2d50061b3bd6eab3f01

Version 1.3.0 works without any issues, so I’ve reverted back to that version for now. We use OAuth2 (keycloak) logins, and I’ve checked for any errors in the logs, but everything looks normal, Thanks!

[zafodB]

We are having the exact same issue, also recently upgraded to 1.4.2.

[enrico-rabeneck]

We have the same issue. The reason is, that one or more cluster are not available. Which leads to the effect, that no cluster is usable. When removing all "broken" clusters the service should work again. But still, its a bug. It should be possible to have clusters down for some time.