Bug 1646871
| Summary: | [OSP] SBD cannot be used with bundles [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.5 | CC: | abeekhof, aherr, autobot-eus-copy, cfeist, cluster-maint, ctowsley, dwojewod, kgaillot, kwenning, michele, mkrcmari, sbradley |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | 7.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.18-11.el7_5.4 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: When SBD is configured on the cluster nodes, Pacemaker Remote nodes (including guest nodes and bundle nodes) will compare the local SBD configuration and abort if not compatible.
Consequence: Guest nodes and bundle nodes unnecessarily fail when SBD is used on the cluster nodes, since they use resource recovery rather than standard fencing mechanisms.
Fix: Pacemaker Remote skips the SBD compatibility check when run on a guest node or bundle node.
Result: Guest nodes and bundle nodes may be used in a cluster with SBD, without configuring SBD on the guest nodes or bundle nodes themselves.
|
Story Points: | --- |
| Clone Of: | 1638593 | Environment: | |
| Last Closed: | 2018-12-18 14:46:19 UTC | Type: | --- |
| 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: | 1638593 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-11-06 08:08:24 UTC
Fixed in upstream 1.1 branch by commit 4dae674 QA: To reproduce, configure a cluster with a guest node and/or bundle, where all the cluster nodes use sbd for fencing. Configure a resource to run on the guest node and/or in the bundle that will require contacting the CIB or controller, such as galera, redis, or rabbitmq (or a modified Dummy resource that calls something like cibadmin -Q). Before the fix, the guest node and/or bundle instance will get restarted when the resource starts on it; after the fix, it will proceed normally. *** Bug 1656731 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-2018:3844 |