Bug 1042808
| Summary: | [RHSC] After failure of a remove-brick task on a volume, attempts to start subsequent tasks on the volume fail. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> |
| Component: | rhsc | Assignee: | Alok <asrivast> |
| Status: | CLOSED CANTFIX | QA Contact: | Anoop <annair> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | anbabu, asriram, knarra, ltrilety, mmahoney, mmccune, rhs-bugs, sabose, sankarshan, sdharane |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhsc-3.1.0-59 | Doc Type: | Known Issue |
| Doc Text: |
When remove-brick operation fails on a volume, the Red Hat Storage node does not allow any other operation on that volume.
Workaround: Perform "commit" or "stop" for the failed remove-brick task, before another task can be started on the volume.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-29 15:14:02 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: | |
| Embargoed: | |||
| Bug Depends On: | 1042777, 1294033, 1351102 | ||
| Bug Blocks: | 1035040, 1202842 | ||
|
Description
Shruti Sampat
2013-12-13 12:29:26 UTC
This behaviour should be documented in the Administration guide of RHSC Along with the work around of going to the gluster CLI and running the stop command as given in the BZ 1042777 Please review the edited doc text and sign off. Made a slight correction in the doc-text. It looks fine now. So, the error returned by gluster is "A remove-brick task on volume remove-brick is not yet committed. Either commit or stop the remove-brick task." But frontend is not showing this error.So I think its better to show the same error in the UI rather than we taking a call whether to commit or stop remove-brick operation (In reply to anmol babu from comment #5) > So, the error returned by gluster is "A remove-brick task on volume > remove-brick is not yet committed. Either commit or stop the remove-brick > task." > But frontend is not showing this error.So I think its better to show the > same error in the UI rather than we taking a call whether to commit or stop > remove-brick operation Sounds good to me. Please provide the fixed in version. This was wrongly moved to ON_QA and hence moved it back to Assigned. The fix is in master but needs to backported. Removing FailedQA as QE din't verify this I do not see the fix which is mentioned in comment 5 ? Has this been changed? Moving this back since the expected results does not match with actual ones. BTW Failed remove-brick task is not possible to stop, commit or retain from GUI as all those actions are disabled. So just to tell that rebalance cannot be run till stop or commit will be done doesn't help much. Thank you for your report. This bug is filed against a component for which no further new development is being undertaken |