Bug 1637445
Summary: | Brick process not coming up after force starting volume due to stale port map entries | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Upasana <ubansal> |
Component: | glusterd | Assignee: | Mohit Agrawal <moagrawa> |
Status: | CLOSED ERRATA | QA Contact: | Upasana <ubansal> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.4 | CC: | amukherj, nchilaka, rhs-bugs, sankarshan, storage-qa-internal, ubansal, vbellur |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.4.z Batch Update 3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.2-33 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-04 07:41:25 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
Upasana
2018-10-09 09:45:35 UTC
I'll get this bug picked up once I look at BZ 1637379 as that seems to be the originating source of the problem in the setup. Do you still have the set up? If yes, I'd like you to get me the output of following: Considering Brick 10.70.35.36:/gluster/brick1/vol_-9-1 is showing N/A, please take output of cat /var/run/gluster/vols/vol_-9-1/<pidfile> . If you see the file and a number inside it, do a ps aux | grep <pid number>. On a different note, I couldn't find out this volume is being force started from cmd_history.log file. Also can you/Nag justify the reason of marking this as severity urgent? upstream patch : https://review.gluster.org/#/c/21568/ 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-2019:0263 |