Bug 894292 - [RHSC] Events log messages seen in Improper order while creating a volume from UI
Summary: [RHSC] Events log messages seen in Improper order while creating a volume fro...
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: 921020
TreeView+ depends on / blocked
 
Reported: 2013-01-11 10:48 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:
: 921020 (view as bug list)
Environment:
Last Closed: 2013-09-23 22:25:33 UTC
Embargoed:


Attachments (Terms of Use)
screenshot of Events log (137.89 KB, image/png)
2013-01-11 10:48 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2013-01-11 10:48:39 UTC
Created attachment 676785 [details]
screenshot of Events log

Description of problem:
---------------------------------------
When a volume is created from the Console, the Events log reports messages for setting of volume options (auth.allow, nfs.disable, user.cifs) for the newly created volume, before the message for volume creation is seen.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a volume from the Console
  
Actual results:
Events log messages seen in the above described order.

Expected results:
Message for volume creation should be seen first and then messages for setting of volume options.

Additional info:

Comment 2 Shireesh 2013-01-11 15:41:06 UTC
Upstream patch: http://gerrit.ovirt.org/10907

Comment 3 Shruti Sampat 2013-01-30 10:44:43 UTC
Verfied in Red Hat Storage Console Version: 2.1.0-0.qa5.el6rhs. Events log messages now seen in the following order - 
1. creation of volume
2. setting of volume options (if any) done during creation

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.