Bug 1595144

Summary: Exceptions seen with refreshing geo-rep session on the gluster volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: rhhiv-1.5CC: bugs, godas, pstehlik, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1595140 Environment:
Last Closed: 2019-05-20 04:54:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1595140    
Bug Blocks: 1520836    

Description SATHEESARAN 2018-06-26 08:43:01 UTC 
+++ This bug was initially created as a clone of Bug #1595140 +++

Description of problem:
------------------------
There are 2 geo-rep sessions created for the gluster volume from backend and those gluster nodes are managed in oVirt manager in a virt+gluster service enabled cluster. When refreshing geo-rep session sync from manager UI, the operation failed, when checking the engine.log found the trace of exception

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

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Manage gluster node in oVirt Manager
2. Create gluster volume
3. Create 2 geo-rep session for that volume with 2 slave gluster volumes
4. From the oVirt Manager UI, click on 'sync' on that gluster volume under geo-replication tab

Actual results:
---------------
Failed to sync the available geo-rep sessions

Expected results:
-----------------
All the geo-rep session should have been synced 
Additional info:
Comment 4 SATHEESARAN 2018-10-17 01:35:06 UTC 
This bug was originally fixed with RHV 4.2.6, but missed verification during that time.

Tested with RHV 4.2.6-4 and glusterfs-3.8.4-54.15
While trying to sync the geo-rep session created from gluster CLI, it got synced successfully with RHV Manager UI. There are no exceptions