Bug 891903 - [RHSC] Events message seen on tagging a volume as image store could be improved
Summary: [RHSC] Events message seen on tagging a volume as image store could be improved
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: 921065
TreeView+ depends on / blocked
 
Reported: 2013-01-04 11:55 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:
: 921065 (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:55 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2013-01-04 11:55:25 UTC
Created attachment 672378 [details]
engine logs

Description of problem:
---------------------------------------
On tagging a volume as an image store by clicking on 'Optimize for Virt Store', the following message is seen thrice on the Events tab - 
"Volume Option set on <vol-name>."

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 'Optimize for Virt Store' button.
  
Actual results:
The message described above is seen thrice on the Events tab.

Expected results:
The above message could be improved by adding the name of the volume option that is being set.

Additional info:

Comment 2 Shireesh 2013-01-17 13:52:44 UTC
This is not just specific to 'Optimize for Virt Store', but happens whenever an option is set from the UI e.g. during volume creation, or when user explicitly sets any option of a volume.

Following upstream patch fixes this: http://gerrit.ovirt.org/10908

Comment 3 Shruti Sampat 2013-02-01 12:13:46 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.