+++ This bug was initially created as a clone of Bug #1343650 +++

Description of problem:
=======================

With the latest build, the creation of geo-replication fails and status goes to unknown state. Also, setting up the configuration (like use_meta_volume true) also fails.

This has worked with earlier 3.1.3 builds: glusterfs-3.7.9-4. Screenshot and logs will be updated. 


Version-Release number of selected component (if applicable):
=============================================================
RHSC: 3.1.3-0.72.el6
GLusterfs: glusterfs-3.7.9-8


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. From UI, Setup master and slave cluster
2. Create Master and Slave volume
3. Setup Geo-Rep between Master and Slave Volume

Actual results:
===============

Geo-Rep goes to UNKNOWN State. Also, setting up any config option fails.


Expected results:
================

Geo-Replication should be successful

Additional Info:
================

With Same RHSC Version: 3.1.3-0.72.el6 and older gluster version: glusterfs-3.7.9-4, it works.


--- Additional comment from Ramesh N on 2016-06-08 00:28:15 EDT ---

This bug is a result of a recent change in gluster cli output for 'gep rep status'. Slave volume ID is added to geo rep session key. We have to change our gluster CLI output parsing in VDSM and RHSC.

Old Geo rep Session Key: 'b1b92a4e-ce58-4b9d-ac3b-a8c693bca029:ssh://10.70.37.190::slave'

New Geo rep Session Key: 'b1b92a4e-ce58-4b9d-ac3b-a8c693bca029:ssh://10.70.37.190::slave:bd52ddf1-9659-4168-8197-c62e9f3e855c'