Bug 1570618
Summary: | Pending notify actions are recorded as complete [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: | Marc Muehlfeld <mmuehlfe> | |
Priority: | urgent | |||
Version: | 7.5 | CC: | abeekhof, aherr, amit.banerjee, cluster-maint, kgaillot, mjuricek, mnovacek | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | 7.5 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | pacemaker-1.1.18-11.el7_5.2 | Doc Type: | Bug Fix | |
Doc Text: |
To ignore the result of clone notify actions, Pacemaker reports them always as successfully completed. However, when the record-pending setting was set to true, which is the default, Pacemaker incorrectly reported pending clone notifications as successfully completed which led to "old event" warnings and unnecessary transition restarts. With this update, Pacemaker only records completed, not pending, clone notify actions as successful. As a result, the correct ordering of actions is preserved if the record-pending setting is enabled.
|
Story Points: | --- | |
Clone Of: | 1570130 | |||
: | 1571765 (view as bug list) | 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: | 1570130 | |||
Bug Blocks: | 1571765 |
Description
Oneata Mircea Teodor
2018-04-23 10:56:47 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, 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 |