Bug 1187128

Summary: Value displayed in slave column of geo-replication status command is inconsistent.
Product: [Community] GlusterFS Reporter: Darshan <dnarayan>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.1CC: bugs, gluster-bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-01 09:32:15 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 Darshan 2015-01-29 11:49:37 UTC 
Description of problem: 
The column named SLAVE in geo-replication status output shows the values in a inconsistent way. some times the hostname is prefixed with "ssh://" sometimes just the hostname is displayed.

eg:

1. without prefix:

MASTER NODE                         MASTER VOL    MASTER BRICK    SLAVE                      STATUS         CHECKPOINT STATUS    CRAWL STATUS        
----------------------------------------------------------------------------------------------------------------------------------------------
dhcp42-98.lab.eng.blr.redhat.com    vol1          /bricks/b1      10.70.42.104::slavevol1    Not Started    N/A                  N/A 
**********************

2. With prefix:

MASTER NODE                         MASTER VOL    MASTER BRICK    SLAVE                            STATUS         CHECKPOINT STATUS    CRAWL STATUS        
----------------------------------------------------------------------------------------------------------------------------------------------------
dhcp42-98.lab.eng.blr.redhat.com    vol1          /bricks/b1      ssh://10.70.42.104::slavevol1    Not Started    N/A                  N/A
*****************************
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results: The output in SLAVE column should be consistent and it should not be prefixed with "ssh://".


Additional info: This issue has to be addressed in --xml output as well.
Comment 1 Aravinda VK 2015-09-01 09:32:15 UTC 
New Column is introduced in Geo-rep Status called "SLAVE NODE" which will show to which Slave node a Geo-rep worker is connected. Default value is "N/A" in case Worker is not in Active/Passive state. "SLAVE" column will always shows the the Slave details used in session creation.

Closing this bug since it is fixed with 3.7 release. Please reopen if found again.