Bug 1029472

Summary: clicking on commit does not result in the commit window being opened.
Product: Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: anmol babu <anbabu>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: dpati, dtsang, mmahoney, pprakash, rhs-bugs, ssampat
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cb10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 08:03:12 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:

Description RamaKasturi 2013-11-12 12:50:49 UTC 
Description of problem:
clicking on commit  does not result in the commit window being opened.

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.23.master.el6_5.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a distribute volume and start it.
2. Now add a brick to the volume say /tmp/b10.
3. Now remove the brick which was added i.e. /tmp/b10.
4. Once remove brick is started click on status button from the drop down.
5. Now click on commit button from the status dialog.

Actual results:
Clicking on commit results to nothing.

Expected results:
clicking on commit should commit the bricks. Since the data migration is completed commit and retain should work fine.

Additional info:
Comment 1 RamaKasturi 2013-11-12 12:55:01 UTC 
Please find the sos report in the following link

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1029472/
Comment 3 RamaKasturi 2013-12-13 11:05:31 UTC 
Verified and woks fine in cb11 rhsc-2.1.2-0.27.beta.el6_5.noarch. 

Clicking on commit, opens up commit dialog box and sucessfully able to commit the brick.
Comment 5 errata-xmlrpc 2014-02-25 08:03:12 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/RHEA-2014-0208.html