Bug 1566533
| Summary: | pacemaker can get in a state where a remote is unable to connect to the cluster [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: | pkomarov |
| Severity: | urgent | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | urgent | ||
| Version: | 7.5 | CC: | abeekhof, aherr, cluster-maint, kgaillot, michele, mjuricek, mkrcmari, oblaut, sbradley |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | 7.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.18-11.el7_5.1 | Doc Type: | Bug Fix |
| Doc Text: |
In certain situations, Pacemaker cleared the fail counter of a remote node before the node was successfully fenced. Thus, a subsequent reconnect failed when the attempt was tried between error cleaning and the actual fencing. A very low value set in the reconnect_interval option increased the chance of this situation. Consequently, Pacemaker was unable to reconnect to the remote host. With this update, Pacemaker now delays resource failure time outs until pending fencing actions are completed. As a result, the described scenario no longer appears and remote nodes are correctly recovered.
|
Story Points: | --- |
| Clone Of: | 1565187 | Environment: | |
| Last Closed: | 2018-05-14 16:13:02 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: | 1565187 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-12 13:26:10 UTC
Verified , Tested cluster integrity on all nodes after compute failover environment details : pacemaker-libs-1.1.18-11.el7.x86_64 osp13 core_puddle_version:2018-04-19.2 With instance-ha deployed . 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:1404 |