-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
In some situations, the KafkaRoller issues confusing log messages. For example in a case like this:
2022-08-02 20:07:47 INFO KafkaRoller:569 - Reconciliation #1(watch) Kafka(myproject/my-cluster): Dynamic reconfiguration for broker 0 was successful. 2022-08-02 20:07:47 INFO KafkaRoller:306 - Reconciliation #1(watch) Kafka(myproject/my-cluster): Could not roll pod {my-cluster-kafka-1} due to io.strimzi.operator.cluster.operator.resource.KafkaRoller$ForceableProblem: Pod my-cluster-kafka-1 is currently the controller and there are other pods still to roll, retrying after at least 250ms 2022-08-02 20:07:48 INFO KafkaRoller:569 - Reconciliation #1(watch) Kafka(myproject/my-cluster): Dynamic reconfiguration for broker 2 was successful. 2022-08-02 20:07:48 INFO KafkaRoller:569 - Reconciliation #1(watch) Kafka(myproject/my-cluster): Dynamic reconfiguration for broker 1 was successful.
There was never any need for rolling update as the dynamic configuration was sufficient. However, a log message which can easily confuse a user talks about not being able to roll a pod.
Would it be possible to log this message only in case some logging is actually needed?
