Bug 1751717
Summary: | Host activation causes RHHI nodes to lose the quorum | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
Component: | rhhi | Assignee: | Gobinda Das <godas> |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.4 | CC: | godas, mmuench, nravinas, rhs-bugs, seamurph |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHHI-V 1.6.z Async Update | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.3.6.6 | Doc Type: | Bug Fix |
Doc Text: |
Previously, the gluster service was started during host activation even when it had not previously been stopped. This restart caused volumes to lose quorum and stop working. The state of the gluster service is now checked during host activation, and the service is started only if it was previously stopped, which avoids this issue.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-03 12:24:16 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: | 1751142 | ||
Bug Blocks: |
Description
SATHEESARAN
2019-09-12 13:01:20 UTC
The dependent bug is already ON_QA Verified with RHV 4.3.6.6 with the following steps 1. Created a HC cluster 2. Move the HC node in to MAINTENANCE, without stopping gluster services 3. Note the PID of glusterd process and brick process. 4. Activate the host back Observed that the gluster process PID remained the same post the host is activated *** Bug 1746789 has been marked as a duplicate of this bug. *** 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:2963 |