Bug 1213703 - geo-replication status xml output has incorrect grouping of pairs under sessions.
Summary: geo-replication status xml output has incorrect grouping of pairs under sessi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 06:06 UTC by Darshan
Modified: 2015-05-18 10:47 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.7.0beta2
Clone Of:
Environment:
Last Closed: 2015-05-18 10:47:10 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
A sample of xml output where the issue is seen. (6.80 KB, text/plain)
2015-04-21 06:06 UTC, Darshan
no flags Details

Description Darshan 2015-04-21 06:06:00 UTC
Created attachment 1016688 [details]
A sample of xml output where the issue is seen.

Description of problem:
In situations where slave volume is made up of bricks in multiple nodes, geo-replication status xml output gives incorrectly grouped pairs under sessions.
ovirt consumes this xml output and it needs properly grouped sessions.

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


How reproducible:
Not consistently reproducible, but this issue is frequently seen.

Steps to Reproduce:
1. 
2.
3.

Actual results:
Each pair is shown as a separate session, in above mentioned case.

Expected results:
Pairs has to be properly grouped under a session.

Additional info:

Comment 1 Anand Avati 2015-04-29 17:00:10 UTC
REVIEW: http://review.gluster.org/10451 (geo-rep: Status output sort based on slavekey) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Aravinda VK 2015-05-10 03:51:34 UTC
Fixed this as part of Status Enhancement http://review.gluster.org/#/c/10574/

Comment 3 Aravinda VK 2015-05-18 10:47:10 UTC
This bug is getting closed because a release has been made available that
should address the reported issue. In case the problem is still not fixed with
glusterfs-3.7.0, please open a new bug report.


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