Bug 1368829 - while scheduling gluster snapshots, 'recurrence' fields lists the dropdown filled with incorrect enum
Summary: while scheduling gluster snapshots, 'recurrence' fields lists the dropdown fi...
Keywords:
Status: CLOSED DUPLICATE of bug 1269132
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.2.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-21 17:38 UTC by SATHEESARAN
Modified: 2016-08-22 09:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-22 09:12:21 UTC
oVirt Team: Gluster
Embargoed:
sasundar: planning_ack?
sasundar: devel_ack?
sasundar: testing_ack?


Attachments (Terms of Use)
scheduling gluster volume snapshots window (37.53 KB, image/png)
2016-08-21 17:40 UTC, SATHEESARAN
no flags Details

Description SATHEESARAN 2016-08-21 17:38:48 UTC
Description of problem:
-----------------------
While scheduling the gluster volume snapshot from RHV UI, the recurrence field which has a dropdown, is filled with 'Incorrect enum' as values.


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

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

Steps to Reproduce:
-------------------
1. Add RHGS/Gluster node to 3.6 cluster
2. Create a replica 3 volume
3. Schedule gluster volume snapshot on that volume from RHV UI

Actual results:
----------------
While scheduling the snapshots, the 'recurrence' dropdown filed is filled with 'Incorrect Enum' as values

Expected results:
-----------------
'recurrence' field should be filled with proper values

Comment 1 SATHEESARAN 2016-08-21 17:40:44 UTC
Created attachment 1192628 [details]
scheduling gluster volume snapshots window

Comment 2 Ramesh N 2016-08-22 09:12:21 UTC
This is a duplicate of bz#1269132. We had some issues with the Enum translation all these issues will be fixed as part of bz#1269132

*** This bug has been marked as a duplicate of bug 1269132 ***


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