Bug 1061651 - Tech-preview warning is not shown for Stop remove-brick operation
Summary: Tech-preview warning is not shown for Stop remove-brick operation
Keywords:
Status: CLOSED DUPLICATE of bug 1060991
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 2.1.2
Assignee: Kanagaraj
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-05 10:32 UTC by Kanagaraj
Modified: 2016-04-18 10:06 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-11 05:43:18 UTC
Embargoed:

Attachments (Terms of Use)

Description Kanagaraj 2014-02-05 10:32:11 UTC 
Description of problem:
While stopping a remove brick operation, 'technology preview' warning is not shown even though this feature is in tech-preview in RHS

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a distribute volume with 2 bricks
2. Remove one of the bricks with migration
3. Click on stop remove-brick

Actual results:
Stop remove-brick confirmation is shown without tech-preview warning.

Expected results:
Stop remove-brick confirmation should have tech-preview warning.

Additional info:
Comment 1 Dusmant 2014-02-07 10:12:11 UTC 
*** Bug 1060991 has been marked as a duplicate of this bug. ***
Comment 2 Jay Turner 2014-02-10 16:15:17 UTC 
I'm confused by the move to POST and the corresponding external link to gerrit 19338.  That patch has nothing to do with this issue, at least not as far as I can tell.  Instead it removes a Fedora 19 requires and lists a java directory as being part of the package.  Was the move to POST and inclusion of that patch done in error?
Comment 3 Kanagaraj 2014-02-10 17:28:58 UTC 
Sorry it was my mistake.
I have added ovirt gerrit instead of internal gerrit in the external tracker.
Comment 4 Kanagaraj 2014-02-11 05:43:18 UTC 

*** This bug has been marked as a duplicate of bug 1060991 ***
Note You need to log in before you can comment on or make changes to this bug.