Subject: Issue with "Offline" cluster visibility after upgrading to 1.4.2 (Regression vs 1.3.0)

[Ganiballis]

Hello team,

I am encountering an issue regarding the display of unavailable clusters after upgrading from version 1.3.0 to 1.4.2.

The Problem: In version 1.3.0, if a Kafka cluster was unavailable, the UI correctly displayed it with an "Offline" status. However, after deploying version 1.4.2, unavailable clusters are not displayed in the UI as "Offline" as expected.

Logs: I am observing the following error in the backend logs: Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: listNodes (I have attached the full error log in the errors file).

Configuration: I have attached my application-local configuration file. This is the configuration I use to launch these versions.

Questions:

Is this a known regression in 1.4.2?

Has the logic for handling connection timeouts changed?

Is there a specific configuration parameter added in 1.4.2 that I need to set to restore the "Offline" badge behavior instead of the UI failing to list the cluster?

Any advice would be appreciated.

Thank you.
1.3.0.bmp
1.4.2.bmp
application-local.yaml
errors.txt