When deploying Kafka and Zookeeper, removing the relation and re-adding the relation, not all the Kafka nodes come up healthy. Analysis of the logs suggest that non-leader are not able to authenticate to zookeeper. Indeed the zookeeper-jaas.cfg file on non-leader nodes keep having the old username and password.
We provide a bundle to reproduced attached to the issue.
Steps to reproduce
juju deploy bundle.yaml
(wait for everything to go into a idle/active state)
juju remove-relation kafka zookeeper
juju relate kafka zookeeper
Expected behavior
The kafka cluster comes back online healthy, with all nodes up and running.
When deploying Kafka and Zookeeper, removing the relation and re-adding the relation, not all the Kafka nodes come up healthy. Analysis of the logs suggest that non-leader are not able to authenticate to zookeeper. Indeed the
zookeeper-jaas.cfg
file on non-leader nodes keep having the old username and password.We provide a bundle to reproduced attached to the issue.
Steps to reproduce
Expected behavior
The kafka cluster comes back online healthy, with all nodes up and running.
Actual behavior
The non leader units report
Versions
Operating system: 22.04
Juju CLI: 3.4/stable
Juju agent: 3.4.4
Charm revision: Kafka 177 and ZooKeeper 134
LXD: 5.0.3
bundle.yaml.txt