Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1519335 - When trying to add bricks to volume peers' IP's are resolved improperly
Summary: When trying to add bricks to volume peers' IP's are resolved improperly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Gaurav Yadav
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-30 15:39 UTC by Damian Wojsław
Modified: 2017-12-01 09:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-01 09:07:01 UTC


Attachments (Terms of Use)

Description Damian Wojsław 2017-11-30 15:39:46 UTC
Description of problem:
Customer tries to add bricks to gluster in RHHI setup. They have created bricks by UI and tried to start volume with added bricks, but logs say that peers are not in connected state. 
Peer files say that they are connected. What is interesting though is that systems seems to have cached wrong IP addresses somehow.


Version-Release number of selected component (if applicable):
glusterfs-3.8.4-18.7.el7rhgs.x86_64                         Wed Nov  1 21:28:30 2017
glusterfs-api-3.8.4-18.7.el7rhgs.x86_64                     Wed Nov  1 21:28:31 2017
glusterfs-cli-3.8.4-18.7.el7rhgs.x86_64                     Wed Nov  1 21:23:27 2017
glusterfs-client-xlators-3.8.4-18.7.el7rhgs.x86_64          Wed Nov  1 21:23:29 2017
glusterfs-fuse-3.8.4-18.7.el7rhgs.x86_64                    Wed Nov  1 21:30:07 2017
glusterfs-geo-replication-3.8.4-18.7.el7rhgs.x86_64         Wed Nov  1 21:33:44 2017
glusterfs-libs-3.8.4-18.7.el7rhgs.x86_64                    Wed Nov  1 21:23:24 2017
glusterfs-rdma-3.8.4-18.7.el7rhgs.x86_64                    Wed Nov  1 21:31:43 2017
glusterfs-server-3.8.4-18.7.el7rhgs.x86_64                  Wed Nov  1 21:33:43 2017

Thing to note is that the wrong IP is part of management network for Gluster.

How reproducible:
Always

Steps to Reproduce:
1. Remove peers from pool
2. Add their IPs to /etc/hosts
3. Try to probe peers, their IPs are wrong.

Actual results:
Error in logs Peer not in connected state with wrong IP as hostname

Expected results:
Peers probed, pool created, volume started.



Additional info:
In next comment


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