Bug 1545277
Summary: | Brick process crashed after upgrade from RHGS-3.3.1 async(7.4) to RHGS-3.4(7.5) | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rajesh Madaka <rmadaka> | |
Component: | core | Assignee: | Mohit Agrawal <moagrawa> | |
Status: | CLOSED ERRATA | QA Contact: | Rajesh Madaka <rmadaka> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.4 | CC: | amukherj, rhinduja, rhs-bugs, sasundar, slenzen, storage-qa-internal | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | brick-multiplexing | |||
Fixed In Version: | glusterfs-3.12.2-8 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1583937 (view as bug list) | Environment: | ||
Last Closed: | 2018-09-04 06:42:41 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: | 1503137, 1583937 |
Description
Rajesh Madaka
2018-02-14 14:21:13 UTC
copied brick logs and sosreport of upgraded in below path: qe.eng.blr.redhat.com:/var/www/html/sosreports/rajesh/1545277 I have followed the steps mentioned in above description, i have created same setup(6 node cluster) which is mentioned in desc. i didn't find any brick crashes and all bricks came to online after upgrade. No cores found in all cluster nodes. Verified in below version: glusterfs-server-3.12.2-8 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/RHSA-2018:2607 *** Bug 1763865 has been marked as a duplicate of this bug. *** |