Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1515733 - gdeploy should not pick up hostnames from host list for ctdb deployment if ctdb_nodes is not set
gdeploy should not pick up hostnames from host list for ctdb deployment if ct...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.3
Unspecified Linux
unspecified Severity medium
: ---
: RHGS 3.3.1 Async
Assigned To: Devyani Kota
Manisha Saini
: ZStream
Depends On:
Blocks: 1581561
  Show dependency treegraph
 
Reported: 2017-11-21 04:45 EST by Matthias Muench
Modified: 2018-06-20 23:34 EDT (History)
7 users (show)

See Also:
Fixed In Version: gdeploy-2.0.2-22
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-20 23:33:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1958 None None None 2018-06-20 23:34 EDT

  None (edit)
Description Matthias Muench 2017-11-21 04:45:23 EST
Description of problem:
When using gdeploy to setup ctdb it picks up the list from hosts as ctdb_nodes and stores it into /etc/ctdb/nodes, regardless of finding hostnames or ip addresses. Since ctdb expects ip address format for entries in /etc/ctdb/nodes it fails to start with error message.

Version-Release number of selected component (if applicable):
gdeploy-2.0.2-14.el7rhgs.noarch

How reproducible:
Always.


Steps to Reproduce:
1. use hostnames instead of ip addresses in [hosts] section of gdeploy config file
2. don't specify ctdb_nodes list
3. run gdeploy 

Actual results:
gdeploy fails with error messages:

PLAY [gluster_servers] ************************************************************************************************************************

TASK [start/stop/restart/reload services] *****************************************************************************************************
failed: [gl-t3] (item=ctdb) => {"failed": true, "item": "ctdb", "msg": "Unable to start service ctdb: Job for ctdb.service failed because the control process exited with error code. See \"systemctl status ctdb.service\" and \"journalctl -xe\" for details.\n"}
failed: [gl-t2] (item=ctdb) => {"failed": true, "item": "ctdb", "msg": "Unable to start service ctdb: Job for ctdb.service failed because the control process exited with error code. See \"systemctl status ctdb.service\" and \"journalctl -xe\" for details.\n"}
failed: [gl-t1] (item=ctdb) => {"failed": true, "item": "ctdb", "msg": "Unable to start service ctdb: Job for ctdb.service failed because the control process exited with error code. See \"systemctl status ctdb.service\" and \"journalctl -xe\" for details.\n"}
	to retry, use: --limit @/tmp/tmpyUmGR5/service_management.retry


and from /var/log/log.ctdb:
2017/11/21 00:44:12.235065 ctdbd[7040]: CTDB starting on node
2017/11/21 00:44:12.236956 ctdbd[7040]: ../ctdb/common/system_util.c:123 Failed to translate gl-t1 into sin_addr
2017/11/21 00:44:12.236973 ctdbd[7040]: Failed to load nodes file "/etc/ctdb/nodes"



Expected results:
gdeploy should not put hostnames into /etc/ctdb/nodes

Additional info:
full trace see https://github.com/mattmuench/bug-traces/blob/master/bug-ctdb_nodes--gdeploy-2.0.2-14
Comment 2 Devyani Kota 2017-12-18 07:10:44 EST
Hi,

PR[1] fixes the issue.
When ctdb_nodes are not set, the default behaviour of gdeploy is to
pick up hosts from the host list.
gdeploy should throw error when hostnames are given instead of IPs
in this case.

[1] https://github.com/gluster/gdeploy/pull/471

Thanks,
Devyani Kota
Comment 8 errata-xmlrpc 2018-06-20 23:33:14 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1958

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