Bug 1635820
Summary: | Seeing defunt translator and discrepancy in volume info when issued from node which doesn't host bricks in that volume | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Sanju <srakonde> | |
Component: | glusterd | Assignee: | Sanju <srakonde> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bmekala, bugs, nchilaka, rhs-bugs, sankarshan, storage-qa-internal, vbellur | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-6.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1635136 | |||
: | 1643052 1647968 (view as bug list) | Environment: | ||
Last Closed: | 2019-03-25 16:31:10 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: | 1635136 | |||
Bug Blocks: | 1643052, 1647968 |
Description
Sanju
2018-10-03 18:15:37 UTC
REVIEW: https://review.gluster.org/21336 (glusterd: ensure volinfo->caps is set to correct value.) posted (#1) for review on master by Sanju Rakonde COMMIT: https://review.gluster.org/21336 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: ensure volinfo->caps is set to correct value. With the commit febf5ed4848, during the volume create op, we are setting volinfo->caps to 0, only if any of the bricks belong to the same node and brickinfo->vg[0] is null. Previously, we used to set volinfo->caps to 0, when either brick doesn't belong to the same node or brickinfo->vg[0] is null. With this patch, we set volinfo->caps to 0, when either brick doesn't belong to the same node or brickinfo->vg[0] is null. (as we do earlier without commit febf5ed4848). fixes: bz#1635820 Change-Id: I00a97415786b775fb088ac45566ad52b402f1a49 Signed-off-by: Sanju Rakonde <srakonde> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/ |