You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As seen above the machine is in AWS and the default hostname is generated in the form ip-internal-ip which is not valid as it does not resolve to anything.
I tried inventory_hostname but it added zk-cluster-01.example.com and then ZK complained w/ "Have smaller server identifier, so dropping the connection".
Hello Simon,
I'm trying not to change the downloaded role as this might make it harder to keep it in sync w/ the future versions.
We have an inventory like:
As seen above the machine is in AWS and the default hostname is generated in the form
ip-internal-ip
which is not valid as it does not resolve to anything.I tried
inventory_hostname
but it addedzk-cluster-01.example.com
and then ZK complained w/ "Have smaller server identifier, so dropping the connection".The only viable solution was
hostvars[host].ansible_all_ipv4_addresses[0]
.(I would have tried
ansible_default_ipv4
but the article https://medium.com/opsops/ansible-default-ipv4-is-not-what-you-think-edb8ab154b10 discouraged me.)I'll make the PR, but I would like to know what path would you like me to take:
zoo.cfg.j2
(like https://github.com/geerlingguy/ansible-role-gitlab/blob/master/defaults/main.yml#L9) oransible_nodename
toansible_all_ipv4_addresses[0]
ansible_nodename
but to something configurable w/ansible_nodename
as default valueThanx!
The text was updated successfully, but these errors were encountered: