| Summary: | 'gluster volume status' command fails on a server after glusterd is brought down and back up, while remove-brick is in progress | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> | ||||
| Component: | glusterfs | Assignee: | Kaushal <kaushal> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Shruti Sampat <ssampat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 2.1 | CC: | dpati, dtsang, kaushal, knarra, mmahoney, pprakash, psriniva, sdharane, vagarwal, vbellur, vraman | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | RHGS 2.1.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | glusterfs-3.4.0.50rhs-1 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, the gluster volume status command would fail on a node when glusterd was restated while remove brick operation was in progress. With this fix, the command works as expected.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1040809 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-02-25 08:01:45 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: | 1040809 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Shruti Sampat
2013-11-07 10:05:47 UTC
Created attachment 820981 [details]
sosreport
Because of this problem, RHSC does not update the icon and task does not get updated Verified as fixed in glusterfs 3.4.0.50rhs. Volume status command is successful after restarting glusterd while remove-brick is in progress. Can you please verify the doc text for technical accuracy? Doc text looks okay. 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 |