Bug 1101942

Summary:	Unable to peer probe 2nd node on distributed volume (3.5.1-0.1.beta1)
Product:	[Community] GlusterFS	Reporter:	Richard <redhat.bugs>
Component:	core	Assignee:	Ric Wheeler <rwheeler>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1113460 (view as bug list)		Environment:
Last Closed:	2014-06-26 08:51:12 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:
Embargoed:

Description Richard 2014-05-28 08:44:25 UTC

Description of problem:

When building a new volume on a brand new server I am unable to peer probe a 2nd node when creating a distributed volume.

Version-Release number of selected component (if applicable):

glusterfs-fuse-3.5.1-0.1.beta1.el6.x86_64
glusterfs-server-3.5.1-0.1.beta1.el6.x86_64
glusterfs-libs-3.5.1-0.1.beta1.el6.x86_64
glusterfs-api-3.5.1-0.1.beta1.el6.x86_64
glusterfs-cli-3.5.1-0.1.beta1.el6.x86_64
glusterfs-3.5.1-0.1.beta1.el6.x86_64

How reproducible:

1. Install the above packages from the Gluster Repo.
2. Create a new volume with 1 node.
3. try and peer probe the 2nd node.

Actual results:

Hostname: 172.16.242.241
Uuid: ad09b6f9-9e71-462b-bec0-bcdc93db221b
State: Probe Sent to Peer (Connected)

and on this node, gluster peer status times out with no output.

Expected results:

the 2nd node should join the pool

Additional info:

This makes GlusterFS UNUSABLE as a distributed filesystem!

Comment 1 Richard 2014-06-16 14:02:45 UTC

Update: Still broken in 3.5.1-beta2.

Comment 2 Richard 2014-06-26 08:51:12 UTC

You can close this bug, I've repreported it for the official 3.5.1 release:
https://bugzilla.redhat.com/show_bug.cgi?id=1113460

*** This bug has been marked as a duplicate of bug 1113460 ***