Bug 1611106
Summary: | Glusterd crashed on a few (master) nodes | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> |
Component: | glusterd | Assignee: | Kotresh HR <khiremat> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.1 | CC: | atumball, bmekala, bugs, khiremat, nbalacha, rallan, rhinduja, rhs-bugs, sankarshan, storage-qa-internal, vbellur, vdas |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-4.1.3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1576392 | Environment: | |
Last Closed: | 2018-08-29 12:44:28 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: | 1570586, 1576392 | ||
Bug Blocks: | 1577868 |
Description
Kotresh HR
2018-08-02 05:07:58 UTC
As we 'agreed' on (ie, no users complained about) removing Tiering from supported state, I recommend marking this test as Bad, or even removing the test itself. REVIEW: https://review.gluster.org/20608 (glusterd/geo-rep: Fix glusterd crash) posted (#1) for review on release-4.1 by Kotresh HR COMMIT: https://review.gluster.org/20608 committed in release-4.1 by "Shyamsundar Ranganathan" <srangana> with a commit message- glusterd/geo-rep: Fix glusterd crash Using strdump instead of gf_strdup crashes during free if mempool is being used. gf_free checks the magic number in the header which will not be taken care if strdup is used. Backport of: > BUG: 1576392 > Change-Id: Iab36496554b838a036af9d863e3f5fd07fd9780e > Signed-off-by: Kotresh HR <khiremat> fixes: bz#1611106 Change-Id: Iab36496554b838a036af9d863e3f5fd07fd9780e Signed-off-by: Kotresh HR <khiremat> 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-4.1.3, please open a new bug report. glusterfs-4.1.3 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/2018-August/000111.html [2] https://www.gluster.org/pipermail/gluster-users/ |