Replies: 1 comment
-
Please share a full log as well as how do you run the User Operator -> as part of a Kafka cluster (in which case please share also the full Kafka custom resource)? As a standalone installation with your own Kafka cluster? |
Beta Was this translation helpful? Give feedback.
0 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.
-
I am using a standalone strimzi operator to connect to my Kafka cluster. Recently I updated the Strzimi Operator from 0.26.1 to 0.27.1. Post the upgrade the user operator is failing giving the below error:
2023-06-08 04:02:41 DEBUG AbstractOperator:610 - Reconciliation #543(watch) KafkaUser(alerting/alert.user): Removed metric strimzi.resource.statealerting:KafkaUser/alert.user
2023-06-08 04:02:41 DEBUG AbstractOperator:618 - Reconciliation #543(watch) KafkaUser(alerting/alert.user): Updated metric strimzi.resource.state[tag(kind=KafkaUser),tag(name=alert.user),tag(reason=Cluster authorization failed.),tag(resource-namespace=alerting)] = 0
2023-06-08 04:02:41 WARN AbstractOperator:532 - Reconciliation #543(watch) KafkaUser(alerting/alert.user): Failed to reconcile
org.apache.kafka.common.errors.ClusterAuthorizationException: Cluster authorization failed.
2023-06-08 04:02:41 DEBUG AbstractOperator:440 - Reconciliation #543(watch) KafkaUser(alerting/alert.user): Lock lock::alerting::KafkaUser::alert.user released
I see the same error for most of the users. The strange part is once I restart the useroperator I dont see this error for some time and again once the periodic reconciliation starts I start seeing this error again.
The older version 0.26.1 works fine on the same setup.
Beta Was this translation helpful? Give feedback.
All reactions