-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: runtime error: index out of range [3] with length 3 #153
Comments
I tried deleting the pod and it loop panic. Here are the logs from start to panic :
|
line 179 of pkg/resources/kafka/configmap.go : Which expect the |
After starting clean I still see the same error for broker 3. The configmap for broker3 is not created.
|
I tried using brokers ID as 0,1,2 instead of 1,2,3... It seems to be running fine. Can you please clarify the usage of broker ID ? does it have to start from 0 (ie it's a counter of brokers starting at 0 OR it's the Kafka Broker ID, which can be any number as long at it's unique) ? |
@prune998 Thanks for reporting this. The first brokerID has to be 0 at the moment. We will fix this soon. |
@prune998 Thanks for reporting this we are going to release a new version soon, which contains the fixes |
OK thanks. |
Describe the bug
During Reconcile of a cluster, the Operator panic with :
Steps to reproduce the issue:
havn't found a way to reproduce yet
Expected behavior
Operator should not panic :)
Additional context
Operator version 0.6.0 generated from Helm chart
Cleaned Zookeeper and re-created the kafka cluster from 0.
I had this error two times, with IDs 121,122,123 then with a new cluster with IDs 1,2,3.
The text was updated successfully, but these errors were encountered: