[Bug]: KafkaConnect cash on init - /opt/kafka/custom-config/kafka-connect.properties: No such file or directory #11311
Closed
WollfieGitHub
started this conversation in
General
Replies: 1 comment 4 replies
-
Hey, this seems like there is some mismatch of the versions. At least I was hitting the same when I for example had old operator running somewhere and I created a new one with KafkaConnect. Could you please share logs of the ClusterOperator? Also, if you can paste here the KafkaConnect CR (not the template). Thanks! |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
Upon creation of the KafkaConnect pod deployed via helm in a minikube-based cluster, I get the error log below which prevents the start of the container:
Steps to reproduce
No response
Expected behavior
No response
Strimzi version
main, 0.45.0
Kubernetes version
Kubernetes 1.29.0
Installation method
Helm Chart
Infrastructure
Minikube
Configuration files and logs
Kafka Connect resource:
Dockerfile used to build the KafkaConnect image, where DEBEZIUM_CONNECT_VERSION is set to
3.1.0.CR1
:Additional context
The issue appeared as I was executing some update scripts and I didn't notice it at first.
I cleaned up the KafkaConnect image in minikube via
minikube image rm
and re-building it, to ensure I had the last strimzi image version, as 5512 mentioned it could be an issue.I applied the latest CRD from
https://github.com/strimzi/strimzi-kafka-operator/tree/main/packaging/helm-charts/helm3/strimzi-kafka-operator/crds
as some other issue mentioned.I will try to provide a clearer way to reproduce the issue later in the week.
Beta Was this translation helpful? Give feedback.
All reactions