Bug 1077646

Summary:	Dist-geo-rep : geo-rep status fails to get status from peers.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Bhaskar Bandari <bbandari>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	aavati, bbandari, csaba, david.macdonald, nlevinki, nsathyan, sdharane, ssamanta, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1077697 (view as bug list)		Environment:
Last Closed:	2014-09-22 19:34:37 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:
Bug Depends On:
Bug Blocks:	1077697

Description Vijaykumar Koppad 2014-03-18 10:56:29 UTC

Description of problem: geo-rep status fails to get status from peers. When you run geo-rep status command, it gets own status only, and fails to get status from peers.


Version-Release number of selected component (if applicable): glusterfs-3.5qa2-0.274.gitecc475d


How reproducible: Happens everytime


Steps to Reproduce:
1. create and start a geo-rep relationship between master and slave 
2. run geo-rep status command
3.

Actual results: It fails to get status from peers


Expected results: It should show status from all the peers. 


Additional info:

Comment 3 Kotresh HR 2014-05-19 06:21:43 UTC

The patch http://review.gluster.org/7289 has the fix.
It is available in downstream.
Fixed in Version: glusterfs-3.6.0.2-1

Comment 4 Vijaykumar Koppad 2014-06-03 12:57:35 UTC

verified in the build glusterfs-3.6.0.10-1.el6rhs

Comment 8 errata-xmlrpc 2014-09-22 19:34:37 UTC

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.

http://rhn.redhat.com/errata/RHEA-2014-1278.html