Bug 1443123
| Summary: | [BrickMultiplex] gluster command not responding and .snaps directory is not visible after executing snapshot related command | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vivek Das <vdas> | |
| Component: | core | Assignee: | Atin Mukherjee <amukherj> | |
| Status: | CLOSED ERRATA | QA Contact: | Vivek Das <vdas> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.3 | CC: | amukherj, nchilaka, rhs-bugs, storage-qa-internal, vdas | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | brick-multiplexing | |||
| Fixed In Version: | glusterfs-3.8.4-24 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1443896 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-21 04:37:54 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: | 1443896, 1444128 | |||
| Bug Blocks: | 1417151 | |||
|
Description
Vivek Das
2017-04-18 14:02:05 UTC
Although I was unable to reproduce this issue, I have a theory behind this and an upstream patch https://review.gluster.org/#/c/17088 has been posted. downstream patch : https://code.engineering.redhat.com/gerrit/#/c/104115/ Updated to the latest gluster version i.e glusterfs-3.8.4-24 followed the steps to reproduce and was not able to see any time out errors. Enabled brick-multiplex stopped and started volume I was able to list snaps I was able to see results for volume status Seems fine to me. So marking this bug as verified. 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. https://access.redhat.com/errata/RHBA-2017:2774 |