Description of problem: If the list of 'hosts' provided to the 'peer' module for action 'probe' uses FQDNs, the node listed in the 'master' value is still probed only by its short hostname. Version-Release number of selected component (if applicable): gdeploy-2.0.2-19 How reproducible: Problem was discovered as part of gluster-colonizer testing, where the 'peer' module is used directly rather than through the gdeploy construct. It has only been observed so far with this deployment method, so I can't confirm yet whether this problem is globally applicable to gdeploy or whether it is something specific to how we are passing values to the module with our ansible play. Steps to Reproduce: 1. Configure ansible play to use the gdeploy 'peer' module to probe nodes based on FQDN 2. Run playbook 3. Observe output of 'gluster pool list' Actual results: The node given for the 'master' value as a FQDN appears in the 'gluster pool list' output with its short hostname and no alias is present in the peer config. Expected results: The 'master' node should appear in the 'gluster pool list' with its FQDN for consistency in node-to-node communication. Additional info:
Since we are deprecating gdeploy in favour of gluster-ansible-roles, this bug is marked to be closed. Please comment if this bug needs attention.
Reason stated in Comment #3.