Bug 1187128 - Value displayed in slave column of geo-replication status command is inconsistent.
Summary: Value displayed in slave column of geo-replication status command is inconsis...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-29 11:49 UTC by Darshan
Modified: 2015-09-01 09:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-09-01 09:32:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.