fix: use the correct zookeeper host for creating SCRAM users when hostname_aliasing_enabled=true #1559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When using hostname aliasing (hostname_aliasing_enabled=true) the create scram users tasks do not use the hostname aliases but instead the public hostname specified in the inventory. As such in cases where the machine we're running those tasks on can only talk to an internal interface and cannot to via the external one, the tasks fail. This PR addresses this by using the same hostname resolution for zookeeper in those tasks as the rest of the playbook
Fixes # (issue)
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: