Bug 1024782

Summary: [RHSC] Retain button in the remove-brick status dialog does not work.
Product: Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sdharane
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cb9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 07:58:16 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:
Bug Depends On:    
Bug Blocks: 1029478    
Attachments:
Description Flags
engine logs none

Description Shruti Sampat 2013-10-30 12:29:31 UTC 
Created attachment 817449 [details]
engine logs

Description of problem:
-----------------------
Retain button in the remove-brick status dialog does not work. Clicking on the retain button does not result in the retain brick dialog to open.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.21.beta1.el6_4 

How reproducible:
Always

Steps to Reproduce:
1. Create a cluster with a single storage node ( to avoid BZ #1020325 )
2. Create a distributed-replicate ( replica 2 ) volume and start it.
3. Start remove-brick operation of a pair of bricks and open the status dialog.

Actual results:
After data migration completes, the Retain and Commit button get enabled, but retain button does not work.

Expected results:
Clicking on the retain button should result in the retain bricks dialog to open.

Additional info:
Comment 2 Shruti Sampat 2013-11-28 09:14:46 UTC 
Verified as fixed in Red Hat Storage Console Version: 2.1.2-0.25.master.el6_5.
Comment 4 errata-xmlrpc 2014-02-25 07:58:16 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