Bug 1337384
| Summary: | Brick processes not getting ports once glusterd comes up. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Byreddy <bsrirama> |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> |
| Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.1 | CC: | asrivast, bsrirama, rcyriac, rhinduja, rhs-bugs, sasundar, storage-qa-internal, vbellur |
| Target Milestone: | --- | Keywords: | Regression, Reopened, ZStream |
| Target Release: | RHGS 3.1.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.9-7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-23 05:23:47 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: | |||
| Bug Blocks: | 1311817 | ||
|
Description
Byreddy
2016-05-19 04:15:07 UTC
We should not be filing bugs with private builds. If you hit the same issue on an official build please mention that otherwise you'd need to close it. (In reply to Atin Mukherjee from comment #5) > We should not be filing bugs with private builds. If you hit the same issue > on an official build please mention that otherwise you'd need to close it. closing based on above comment as NOTABUG. Clearing the flags so as this bug is not listed for bug triage I am reopening this bug because issue found in the provide build is present in the official build "glusterfs-3.7.9-6" as well and setting the required flags back and this is regression b/w the builds "3.7.9-5" and "3.7.9-6" With official build i am seeing little diff in the issue. that is, only bricks part of node where glusterd was down and came up after modifying the volume options on other peer node are not getting the TCP ports. i will provide the required logs ( console and brick log failures ), these is no errors in glusterd log. (In reply to Byreddy from comment #8) > I am reopening this bug because issue found in the private build is present > in the official build "glusterfs-3.7.9-6" as well and setting the required > flags back and this is regression b/w the builds "3.7.9-5" and "3.7.9-6" > > With official build i am seeing little diff in the issue. that is, only > bricks part of node where glusterd was down and came up after modifying the > volume options on other peer node are not getting the TCP ports. > > > i will provide the required logs ( console and brick log failures ), these > is no errors in glusterd log. RCA: Since the downstream backport BZ 1335357 was not a straight forward one (refer to https://code.engineering.redhat.com/gerrit/74663 for more details on why), the patch changed the signature of glusterd_volinfo_copy_brick_portinfo () which lead to zeroing out brickinfo->port while importing a volume. https://code.engineering.redhat.com/gerrit/74996 is posted for review. https://code.engineering.redhat.com/gerrit/74996 is merged now. Verified this bug using the build "glusterfs-3.7.9-7". Fix is working good, Moving to verified state. 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-2016:1240 |