Bug 1636957
| Summary: | peer went into rejected state, if glusterd restarts while creating a volume | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Bala Konda Reddy M <bmekala> |
| Component: | glusterd | Assignee: | Sanju <srakonde> |
| Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.4 | CC: | amukherj, bmekala, rhs-bugs, sanandpa, sankarshan, sheggodu, srakonde, storage-qa-internal, vbellur |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.4.z Batch Update 2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.12.2-27 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-12-17 17:07:11 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: | |||
|
Description
Bala Konda Reddy M
2018-10-08 11:05:13 UTC
1. volume count mismatch - not at all a surprise in this case as glusterd doesn't have any transaction rollback mechanism. So in N1 & N2 the volume create might be through but in N3 it wasn't as glusterd got restarted during commit phase. 3. Peer going into reject state - which peer was showing rejected. Did we check the glusterd log of the node which was rejected? It seems to me that the root cause of this is same as of BZ 1635136 & 1637459 . If so can you please update the bug status with the patch link? upstream patch: https://review.gluster.org/#/c/glusterfs/+/21336/ 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-2018:3827 |