Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1213703

Summary: geo-replication status xml output has incorrect grouping of pairs under sessions.
Product: [Community] GlusterFS Reporter: Darshan <dnarayan>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: bugs, gluster-bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.0beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-18 10:47:10 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:
Attachments:
Description Flags
A sample of xml output where the issue is seen. none

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.