Failed to delete any topic in console v3.0.0

[LeoHsiao1]

Hello, this console is very convenient. But after upgrading to v3.0.0, I can't delete any topic.

Reproduction steps:

1. Deploy a new kafka and console using docker-compose.

   version: '3'
   
   services:
     kafka:
       image: apache/kafka:3.9.0
       environment:
         KAFKA_NODE_ID: 1
         KAFKA_PROCESS_ROLES: broker,controller
         KAFKA_LISTENERS: PLAINTEXT://localhost:9092,CONTROLLER://localhost:9093
         KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092
         KAFKA_CONTROLLER_LISTENER_NAMES: CONTROLLER
         KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT
         KAFKA_CONTROLLER_QUORUM_VOTERS: 1@localhost:9093
       network_mode: host
   
     console:
       image: docker.redpanda.com/redpandadata/console:v3.0.0
       environment:
         KAFKA_BROKERS: 127.0.0.1:9092
       network_mode: host
   

2. Create a topic:

3. Delete this topic and an error will occur:

[LeoHsiao1]

The console container is reporting an error:

console_1  | {"level":"error","ts":"2025-04-23T09:02:21.047Z","msg":"Sending REST error","topic_name":"test","route":"/api/topics/test","method":"DELETE","status_code":503,"remote_address":"10.0.0.1:49492","public_error":"Unexpected Kafka response: No topics set in the response","error":"topics array in response is empty"}
console_1  | {"level":"warn","ts":"2025-04-23T09:02:21.232Z","msg":"","timestamp":"2025-04-23T09:02:21Z","procedure":"/redpanda.api.console.v1alpha1.ClusterStatusService/GetKafkaAuthorizerInfo","request_duration":"1.181039ms","status_code":"internal","request_size_bytes":0,"peer_address":"10.0.0.1:49492","error":"internal: No Authorizer is configured on the broker"}

Meanwhile, browser F12 shows several HTTP requests failed:

[jvorcak]

I wasn’t able to reproduce the issue exactly as described. We’ve fixed the frontend part in https://github.com/redpanda-data/console/pull/1738 where the frontend was incorrectly reporting failed requests as successful.

However, I’d need more information on how to reproduce the issue consistently. The provided docker-compose configuration throws an error for me when I try to run it. Could you please provide more details about your environment setup and any specific steps that might help reproduce the problem reliably?

[LeoHsiao1]

The content of this docker-compose.yml is not special. It merely connects the console to kafka. What error did you encounter when using this docker-compose.yml?

I deployed them on a debian host. The following are the terminal logs:

debian-terminal.log

The last few lines are error reports.

[LeoHsiao1]

Using docker-compose is not the key point. I can also deploy them using docker run:

docker run -d --name kafka --network host \
    -e KAFKA_NODE_ID=1 \
    -e KAFKA_PROCESS_ROLES=broker,controller \
    -e KAFKA_LISTENERS=PLAINTEXT://localhost:9092,CONTROLLER://localhost:9093 \
    -e KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://localhost:9092 \
    -e KAFKA_CONTROLLER_LISTENER_NAMES=CONTROLLER \
    -e KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT \
    -e KAFKA_CONTROLLER_QUORUM_VOTERS=1@localhost:9093 \
    apache/kafka:3.9.0

docker run -d --name console --network host \
    -e KAFKA_BROKERS=127.0.0.1:9092 \
    docker.redpanda.com/redpandadata/console:v3.0.0

[weeco]

Hmm, I checked the error message that says Unexpected Kafka response: No topics set in the response. Indeed this would be a bit unexpected. This case occurs when you send a deletion request to Kafka and the response to that request does not include the topic you requested there.

We haven't changed any code there for a long time. Maybe this would happen if we try to delete a non-existent topic? It's odd. Your docker sample doesn't work on Mac OS, I assume because of the network mode which only seems supported on Linux.

[DzRou]

I have a similar problem, I can't delete the topic through the UI, I get an error, but the topic exists. The installation was done using ansible-playbook cp-kafka without zookeeper, I use kraft

help to solve this problem

[weeco]

I tested it as well with the latest Redpanda version and it's working fine. Turns out this is an issue specific to Apache Kafka, possibly due to a newer supported version of the DeleteTopics request. Will check that, thanks for the report

[LeoHsiao1]

I noticed that v3.1.2 fixed this bug, thank you very much. https://github.com/redpanda-data/console/blob/master/CHANGELOG.md#v312--2025-06-23