Bug 1646350
| Summary: | Clean-up of a managed bundle or guest node resource causes unnecessary recovery [rhel-7.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | Marian Krcmarik <mkrcmari> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, chorn, cluster-maint, cluster-qe, ctowsley, fdinitto, jruemker, kgaillot, kwenning, lmanasko, mjuricek, mnovacek, rmarigny, royoung |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 7.6 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.19-8.el7_6.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, after cleaning a failure history of a managed guest node resource or bundle container, Pacemaker would schedule a re-probe of the resource and recovery of its Pacemaker Remote connection, processed in parallel. As a consequence, Pacemaker Remote connection forced recovery of the guest node resource or bundle container when it was not necessary. With this update, the connection recovery is now scheduled after the re-probe result. As a result, in case the re-probe does not find anything wrong, the recovery does not start.
|
Story Points: | --- |
| Clone Of: | 1448467 | Environment: | |
| Last Closed: | 2018-11-27 01:21:58 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: | 1448467 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-11-05 12:36:30 UTC
Fixed in upstream 1.1 branch by commits a07ff46, fade228, and af4f6a1 QA: Configure and start a cluster with a guest node and/or bundle, then run "pcs resource refresh" on the guest node resource and/or bundle resource. It would also be sufficient to force the resource to have a failure then run "pcs resource cleanup". Before the fix, the guest node or bundle will get restarted; after the fix, it won't. 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:3667 |