| Summary: | RHS-C: Remove-brick of second brick in a volume is also trying to remove the brick that was already Retained | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> | ||||||
| Component: | rhsc | Assignee: | Ramesh N <rnachimu> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 2.1 | CC: | dtsang, knarra, mmahoney, pprakash, rhs-bugs, ssampat | ||||||
| Target Milestone: | --- | Keywords: | ZStream | ||||||
| Target Release: | RHGS 2.1.2 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Cb6 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-02-25 07:44:08 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: | |||||||
| Attachments: |
|
||||||||
Created attachment 815413 [details]
screenshot2
Verified in cb6. New feature hence no doc text required 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 |
Created attachment 815412 [details] screenshot1 Description of problem: Remove-brick of second brick in a volume is also trying to remove the brick that was already removed and Retained Version-Release number of selected component (if applicable): [root@vm08 /]# rpm -qa |grep rhsc rhsc-webadmin-portal-2.1.2-0.21.beta1.el6_4.noarch rhsc-lib-2.1.2-0.21.beta1.el6_4.noarch rhsc-log-collector-2.1.2.0-0.1.el6rhs.noarch rhsc-branding-rhs-3.3.0-1.0.master.201309200500.fc18.noarch rhsc-dbscripts-2.1.2-0.21.beta1.el6_4.noarch rhsc-2.1.2-0.21.beta1.el6_4.noarch rhsc-cli-2.1.0.0-0.bb3a.el6rhs.noarch rhsc-backend-2.1.2-0.21.beta1.el6_4.noarch rhsc-setup-2.1.2-0.21.beta1.el6_4.noarch rhsc-sdk-python-2.1.2.0-0.1.el6rhs.noarch rhsc-restapi-2.1.2-0.21.beta1.el6_4.noarch rhsc-tools-2.1.2-0.21.beta1.el6_4.noarch vdsm-4.13.0-19.gitc2a87f5.el6rhs.x86_64 glusterfs-3.4.0.35.1u2rhs-1 How reproducible: Always Steps to Reproduce: 1. Create a distribute volume having 2 bricks (say brick1 and brick2) and start it. 2. In the Bricks sub-tab select one of the bricks (say brick1) and click on Remove. 3. After data migration is complete, click on the drop-down beside the icon that appears on the row corresponding to that brick selected for removal and click on Retain. 4. After successfully retained, now select the 2nd brick (brick2) for removal and click on Remove. 5. After data migration is complete, commit the removal of this brick. You will see that both the bricks (brick1 and brick2) are selected for removal. If you proceed further, it will end up in the following error error. See screenshots attached as well. ----- Error while executing action CommitRemoveGlusterVolumeBricks: Volume remove brick commit failed error: Deleting all the bricks of the volume is not allowed ----- Actual results: Expected results: Brick selected for removal in the second remove-brick operation is the one that has to be removed and not the ones retained previously. Additional info: Screenshots attached