Bug 1036566

Summary:	[RFE] : provide a cleaner way to change the storage nodes brick paths in the volume when the hostnames/ip address of the storage node changes
Product:	Red Hat Gluster Storage	Reporter:	spandura
Component:	glusterd	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	amukherj, gyadav, ppai, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Reopened, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-14 14:13:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description spandura 2013-12-02 09:55:46 UTC

Description of problem:
========================
Consider the case where the storage node is stopped and upon restart the storage node gets a new ip_address or hostname. When the node comes back online, the bricks on the storage node is no more valid. This is because currently we recognize each brick by "<IP/Hostname>:<Brick_Directory>". Since the storage node gets a new hostname/ip , the brick paths should also be changed once the node comes back online. 

Version-Release number of selected component (if applicable):
============================================================
glusterfs 3.4.0.44.1u2rhs built on Nov 25 2013 08:17:39

How reproducible:
===============
Often

Steps to Reproduce:
===================
1. Create a 1 x 2 replicate volume . Start the volume. 

2. Stop one of the storage nodes (shutdown). Restart the node. (Restart should change the IP/hostname of the node)

3. The glusterd of the storage node remains the same. The brick paths should be changed since there is change in hostname/ip.

Comment 4 Prashanth Pai 2017-08-11 10:29:00 UTC

This shall be addressed in glusterd2. Here's the upstream issue:
https://github.com/gluster/glusterd2/issues/356

Comment 5 Gaurav Yadav 2017-08-11 11:24:41 UTC

As Atin has already mentioned that glusterd is not able to resolve the bricks on glusterd restart when network interface is down.

We have a similar kind of bug 1472267, which has been addressed and below is the upstream patch for the same.
Upstream patch: https://review.gluster.org/#/c/17813/

Comment 6 Atin Mukherjee 2017-08-14 14:13:59 UTC

Gaurav - Why is this BZ reopened? Please note fix for BZ 1472267 doesn't address this RFE and we'll consider this request only for GlusterD 2.0.