Bug 891896 - [RHSC] Incorrect Events message seen on tagging a volume as an image store
Summary: [RHSC] Incorrect Events message seen on tagging a volume as an image store
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks: 850450 921080
TreeView+ depends on / blocked
 
Reported: 2013-01-04 11:45 UTC by Shruti Sampat
Modified: 2013-09-23 22:25 UTC (History)
6 users (show)

Fixed In Version: qa5
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 921080 (view as bug list)
Environment:
Last Closed: 2013-09-23 22:25:33 UTC
Embargoed:


Attachments (Terms of Use)
engine logs (5.92 MB, text/x-log)
2013-01-04 11:45 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2013-01-04 11:45:21 UTC
Created attachment 672372 [details]
engine logs

Description of problem:
---------------------------------------
When a volume is tagged as an image store, by clicking on the 'Optimize for virt store' button, the following message is seen in the Events tab - 
"Option group was reset on Volume test from gluster CLI. Now reset in engine DB as well."

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1-qa18.el6ev 

How reproducible:
Always

Steps to Reproduce:
1. For a volume, click on the 'Optimize for Virt Store' button.
  
Actual results:
The above described message is seen.

Expected results:
Such a message should not be seen on the Console.

Additional info:

Comment 2 Shireesh 2013-01-21 15:12:34 UTC
Upstream patch: http://gerrit.ovirt.org/11265

Comment 3 Shruti Sampat 2013-02-01 12:13:25 UTC
Verified in Red Hat Storage Console Version: 2.1.0-0.qa5.el6rhs.

Comment 5 Scott Haines 2013-09-23 22:25:33 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html


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