Bug 902334 - [RHSC] During "Optimize for Virt Store", Event says, "Option was set on Volume <VOLNAME> from gluster CLI," even though it was actually set from UI
Summary: [RHSC] During "Optimize for Virt Store", Event says, "Option was set on Volum...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: All
OS: All
medium
low
Target Milestone: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 921077
TreeView+ depends on / blocked
 
Reported: 2013-01-21 11:57 UTC by Prasanth
Modified: 2013-09-23 22:25 UTC (History)
6 users (show)

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


Attachments (Terms of Use)
screenshot of Event messages during the operation (125.10 KB, image/png)
2013-01-21 11:57 UTC, Prasanth
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 11263 0 None None None Never

Description Prasanth 2013-01-21 11:57:28 UTC
Created attachment 684245 [details]
screenshot of Event messages during the operation

Description of problem:

When we click on "Optimize for Virt Store" for any given volume, event says, "Option was set on Volume <VOLNAME> from gluster CLI", even though it was actually set from UI.

Moreover, you can see that these messages are printed more than once. See attached screenshot.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1-0.qa4d.el6rhs 

How reproducible: 100%


Steps to Reproduce:
1. From UI, Select a Volume and click on "Optimize for Virt Store"
2. Now watch the the "Events" messages

  
Actual results: Following is seen in Events:

"Option performance.stat-prefetch=off was set on Volume test from gluster CLI. Now set in engine DB as well."


Expected results: It should be something like:

"Option performance.stat-prefetch=off was set on Volume test from UI. Now set in engine DB as well."


Additional info: Screenshot of "Events" attached.

Comment 3 Shireesh 2013-01-21 15:18:18 UTC
Upstream patch: http://gerrit.ovirt.org/11263

Since the option "group" eventually gets replaced by a set of options from the group file, engine will detect new options, and create event logs for them. The above patch changes the event message to make it more generic, so that it is not misleading. In this case, the messages will now look like:

Detected new option <key=value> on volume <volname> of cluster <clustername>, and added it to engine DB.

Comment 4 Matt Mahoney 2013-02-27 20:13:45 UTC
Validated. The event message now displays as expected.

Comment 6 Scott Haines 2013-09-23 22:25:35 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.