Bug 1639617 - UI Exception observed while syncing geo-rep session from RHVM UI
Summary: UI Exception observed while syncing geo-rep session from RHVM UI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhi-1.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHHI-V 1.5.z Async
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1639618
Blocks: RHHIV-1.5.z-Backlog-BZs
TreeView+ depends on / blocked
 
Reported: 2018-10-16 08:37 UTC by SATHEESARAN
Modified: 2019-05-20 04:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1639618 (view as bug list)
Environment:
Last Closed: 2019-05-20 04:55:27 UTC
Embargoed:


Attachments (Terms of Use)
screenshot showing UI exceptions (45.77 KB, image/png)
2018-10-16 08:37 UTC, SATHEESARAN
no flags Details

Description SATHEESARAN 2018-10-16 08:37:59 UTC
Created attachment 1494286 [details]
screenshot showing UI exceptions

Description of problem:
-----------------------
Geo-rep session was created from CLI of one the node. Sync the geo-rep sesison in RHV Manager UI by doing the following:
Proceed to the RHV Manager UI -> Storage -> volumes -> select the volume, go to 'Geo-replication'  -> Sync

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHV 4.2.7
RHHI 2.0


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

Steps to Reproduce:
-------------------
1. Create a geo-rep session from the CLI on one of the node
2. Sync the session on RHV Manager UI

Actual results:
---------------
UI exception observed


Expected results:
-----------------
No exceptions

Additional info:

Comment 3 SATHEESARAN 2019-01-20 11:49:32 UTC
Tested with RHV 4.2.8, when creating the geo-rep session from the gluster CLI and syncing it in the 
RHV Manager UI, doesn't create any errors or exceptions


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