Skip to content

[ANSIENG-5137] | Fix ZK Chroot creation #2233

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 12, 2025
Merged

[ANSIENG-5137] | Fix ZK Chroot creation #2233

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5f331d6
[ANSIENG-5137] | Fix ZK Chroot creation
rkunwar-28 Sep 21, 2025
ac76349
[ANSIENG-5137] | Update tests for ZK Chroot creation
rkunwar-28 Sep 21, 2025
c389d9a
[ANSIENG-5137] | Fix ZK Chroot creation
rkunwar-28 Nov 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions roles/kafka_broker/tasks/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -432,6 +432,7 @@
# Only runs with zookeeper
- name: Create Zookeeper chroot
shell: >
{% if kafka_broker_final_properties['zookeeper.set.acl']|default('false')|lower == 'true' %}KAFKA_OPTS='-Djava.security.auth.login.config={{kafka_broker.jaas_file}}'{% endif %} \
Copy link
Member

@rrbadiani rrbadiani Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this not caught in molecule tests ?

Copy link
Member

@rrbadiani rrbadiani Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this issue also present in case of zookeeper client authentication being kerberos as there too we are defining the zookeeper.set.acl property in kafka ?

Copy link
Member

@rrbadiani rrbadiani Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can is zookeeper-shell command also fail in these tasks Get Kafka Cluster ID from Zookeeper
or Get Controller Broker ID as there also we have not provided the jaas file as argument ?

Copy link
Member Author

@rkunwar-28 rkunwar-28 Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this not caught in molecule tests ?

In the related incident, the customer's znode was nested:
image

According to the above, the getACL command is telling only zkuser has privilege to w on that particular znode. In ansible playbook, since in most cases znode is only at root this command to create znode doesn't fail in molecule tests, but in case of customer's its nested znode. For this kind of scenario, we need the auth configs to be passed.

is this issue also present in case of zookeeper client authentication being kerberos as there too we are defining the zookeeper.set.acl property in kafka ?

Yes, if a nested znode with similar permissions are used, then we will see this issue since zookeeper.set.acl = true

can is zookeeper-shell command also fail in these tasks Get Kafka Cluster ID from Zookeeper
or Get Controller Broker ID as there also we have not provided the jaas file as argument ?

No, these tasks will not fail

Copy link
Member

@rrbadiani rrbadiani Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets add a nested znode in 1 or few of our test cases as well

Copy link
Member Author

@rkunwar-28 rkunwar-28 Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a molecule test for nested znode is not straightforward. The way our playbooks work, in order to create kafkadev/01, /kafkadev should exist beforehand. So, the playbook must run twice. This was caught during an upgrade scenario and this case can exist in pre-existing clusters. That is why, we have done manual testing for this

Copy link
Member

@rrbadiani rrbadiani Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. probably this can be handled using prepare.yml.
  2. shouldnt this thing be handled in playbook code so that it doesnt fail for customers ?

Copy link
Member

@rrbadiani rrbadiani Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On further discussion now it seems okay to not add additional tests for this. Since this fix is to smoothen some upgrades for users. handling of nested directory paths is not natively supported via cp-ansible and since 8.0 onwards zk is deprecated it doesnt seem worth the effort to add that kind of support

{{ binary_base_path }}/bin/zookeeper-shell {{ hostvars[groups['zookeeper'][0]] | confluent.platform.resolve_hostname }}:{{zookeeper_client_port}} \
{% if zookeeper_ssl_enabled|bool %}-zk-tls-config-file {{ kafka_broker.zookeeper_tls_client_config_file if kafka_broker_secrets_protection_enabled else kafka_broker.config_file }}{% endif %} \
create {{zookeeper_chroot}} ""
Expand Down