Bug 790337

Summary:	Result of `gluster peer status' is inconsistent
Product:	[Community] GlusterFS	Reporter:	Sachidananda Urs <sac>
Component:	glusterd	Assignee:	Vivek Agarwal <vagarwal>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	gluster-bugs, sankarshan, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:46:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	817967

Description Sachidananda Urs 2012-02-14 10:00:04 UTC

Description of problem:

When peer probe is done from different distributions of linux the peer status says `Rejected'/`Not connected' from different machines.

For example consider a FC11 and CentOS6 machines and do a peer probe on them to observe the above results.

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

3.2.x and Mainline.

How reproducible:

Always.

Steps to Reproduce:
1. 5 servers (mixture of FC11 and CentOS6)
2. Peer probe from one of the machines and peer status from each one of them.
  
Actual results:

Peer Rejected / Not connected on peer status

Expected results:

Should show connected from all machines.

Additional info:

This is due to the sort versions on those machines. Statically compiling a version of sort and copying to all the machines solves the issue.

We should implement sort from within our FS than depending on distribution provided sort.

Comment 1 Anand Avati 2012-03-26 21:48:01 UTC

CHANGE: http://review.gluster.com/2990 (mgmt/glusterd: native sort of info files) merged in master by Anand Avati (avati)