Bug 1552750 - gdeploy peer module not probing 'master' host by FQDN
Summary: gdeploy peer module not probing 'master' host by FQDN
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Sachidananda Urs
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1566126
TreeView+ depends on / blocked
 
Reported: 2018-03-07 16:31 UTC by Dustin Black
Modified: 2018-11-15 06:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-15 06:48:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Dustin Black 2018-03-07 16:31:17 UTC
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:

Comment 3 Sachidananda Urs 2018-11-08 07:22:10 UTC
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.

Comment 4 Sachidananda Urs 2018-11-15 06:48:31 UTC
Reason stated in Comment #3.


Note You need to log in before you can comment on or make changes to this bug.