Create or update of a topic that already exists fails if the connection is SSL about ansible-kafka-admin HOT 4 CLOSED

Hey,

Thanks for this issue. I think it is related to python-zk/kazoo#587 which I need to look into.

from ansible-kafka-admin.

Hey @justCatchingRye,

Can you please provide more information your ZK configuration? I am trying to reproduce the issue.

Thank you.

from ansible-kafka-admin.

Hey @StephenSorriaux,

Many thanks for following-up on this. You prompted me to take a closer look at our zookeeper setup and I've found that the issue I was seeing was actually mis-configuration on my side.

We are using AWS MSK (Managed Streaming for Kafka) and I've realised that although our connections to brokers are using TLS, our connections to zookeeper aren't. This is a bit of a surprise, but I realised that when we talk to zookeeper directly we don't actually provide a certificate for the connection. Furthermore, we are connecting to port 2181 and it appears this is the plaintext port.

So, I've resolved the issue in the playbook by removing these lines:

zookeeper_ssl_check_hostname: "{{ssl_check_hostname}}"
zookeeper_ssl_certfile: "{{ssl_certfile}}"
zookeeper_ssl_keyfile: "{{ssl_keyfile}}"

In my problem description I said that creating topics worked, then updates failed. So, this makes sense if I had the zookeeper connection setup using vars that it shouldn't have had, as zookeeper is used in cases where a topic already exists (e.g. an update action). It all makes sense now :)

Thank you very much looking into this and apologies for any time wasted looking into it.

from ansible-kafka-admin.

Thanks a lot for the heads up @justCatchingRye, I am glad to see everything is fine now.

from ansible-kafka-admin.