[Bug]: Error reconciling KafkaTopic null + Broker: Unknown member

[pauloalexandre3d]

Bug Description

We got loads of this error while the reconciliation:
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://172.20.0.1/apis/kafka.strimzi.io/v1beta2/namespaces/kafka/kafkatopics. Message: kafkatopics.kafka.strimzi.io "footopic" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=kafka.strimzi.io, kind=kafkatopics, name=footopic, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=kafkatopics.kafka.strimzi.io "footopic" already exists, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={}). Reconciliation #8317482(periodic -foo) KafkaTopic(kafka/footopic): Error reconciling KafkaTopic null

So it is causing errors when consumers try to commit the offset:
Broker: Coordinator not available

Steps to reproduce

No response

Expected behavior

No errors

Strimzi version

0.30.0

Kubernetes version

Kubernetes 1.26

Installation method

Helm Chart

Infrastructure

Amazon EKS

Configuration files and logs

apiVersion: kafka.strimzi.io/v1beta2
    kind: KafkaTopic
    metadata:
      name: footopic
      labels:
        strimzi.io/cluster: {{ .Release.Name }}
    spec:
      partitions: 60
      replicas: 3
      config:
        retention.ms: 7200000
        segment.bytes: 1073741824`

### Additional context

_No response_

[pauloalexandre3d]

I've realised the auto.create.topics.enable=false configuration. However, I'm not sure about the behaviour of it.
It seems this disable the operator to recreate the topic.

[scholzj]

It is hard to guess what the problem might be without the full logs. That said:

• If you have topic auto creation enabled, it can cause problems with the Topic Operator, especially the old one.
• The Topic Operator was completely rewritten since Strimzi 0.30. So there is not much to do about it unless you manage to reproducer it with the latest Strimzi versions.

[pauloalexandre3d]

Thank you @scholzj for the prompt response.

Adding more logs
2024-05-21 11:58:51 2024-05-21 10:58:51,08209 ERROR [vert.x-eventloop-thread-1] TopicOperator:1490 - Reconciliation #8317050(periodic -footopic) KafkaTopic(kafka/footopic): Error reconciling KafkaTopic null 2024-05-21 11:58:51 at java.lang.Thread.run(Thread.java:829) ~[?:?] 2024-05-21 11:58:51 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[io.netty.netty-common-4.1.77.Final.jar:4.1.77.Final] 2024-05-21 11:58:51 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?] 2024-05-21 11:58:51 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?] 2024-05-21 11:58:51 at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[io.vertx.vertx-core-4.2.4.jar:4.2.4] 2024-05-21 11:58:51 at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:157) ~[io.vertx.vertx-core-4.2.4.jar:4.2.4] 2024-05-21 11:58:51 at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[io.vertx.vertx-core-4.2.4.jar:4.2.4] 2024-05-21 11:58:51 at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:159) ~[io.vertx.vertx-core-4.2.4.jar:4.2.4] 2024-05-21 11:58:51 at io.strimzi.operator.topic.K8sImpl.lambda$createResource$0(K8sImpl.java:51) ~[io.strimzi.topic-operator-0.30.0.jar:0.30.0] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:61) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:83) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:644) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:305) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:518) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:555) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:612) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:661) ~[io.fabric8.kubernetes-client-5.12.2.jar:?] 2024-05-21 11:58:51 at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:682) ~[io.fabric8.kubernetes-client-5.12.2.jar:?]

[pauloalexandre3d]

Closing this discussion. We fixed numerous issues by upgrading to v0.41. Thanks