Bug 1743726
| Summary: | Add configuration option to fix case when sbd is not able to establish cib_connection. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Klaus Wenninger <kwenning> | |
| Component: | sbd | Assignee: | Klaus Wenninger <kwenning> | |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | |
| Severity: | unspecified | Docs Contact: | Steven J. Levine <slevine> | |
| Priority: | unspecified | |||
| Version: | 8.1 | CC: | cfeist, cluster-maint, cluster-qe, jkortus, kgaillot, lmanasko, mlisik, mmazoure, tojeline | |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
|
| Target Release: | 8.3 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | sbd-1.4.1-6.el8 | Doc Type: | Bug Fix | |
| Doc Text: |
For the issue to be resolved we need both the pacemaker & sbd side of the synchronization mechanism.
Synchronization is controlled by a new parameter (SBD_SYNC_RESOURCE_STARTUP) in the sbd-sysconfig-file defaulting to the old behavior.
So if you've edited your sbd-sysconfig-file rpm-update won't pull in the new parameter and you have to manually add the new parameter from the config coming with the sbd-package to get the new behavior.
|
Story Points: | --- | |
| Clone Of: | 1732757 | |||
| : | 1873135 (view as bug list) | Environment: | ||
| Last Closed: | 2020-11-04 04:09:20 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: | 1732757 | |||
| Bug Blocks: | 1718324, 1873135 | |||
|
Comment 6
Klaus Wenninger
2020-07-27 06:07:30 UTC
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 (sbd bug fix and enhancement update), 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-2020:4822 |