Bug 891896

Summary: [RHSC] Incorrect Events message seen on tagging a volume as an image store
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: dtsang, mmahoney, pprakash, rhs-bugs, sdharane, shaines
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: qa5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 921080 (view as bug list) Environment:
Last Closed: 2013-09-23 22:25:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 850450, 921080    
Attachments:
Description Flags
engine logs none

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