Back to bug 1704870

Who When What Removed Added
Red Hat Bugzilla 2019-04-30 17:21:52 UTC Pool ID 0 112
Shane Bradley 2019-04-30 17:23:04 UTC CC sbradley
Ken Gaillot 2019-05-09 22:02:39 UTC Flags needinfo?(sbradley)
Andrew Beekhof 2019-05-10 02:51:38 UTC Flags needinfo?(sbradley)
Andrew Beekhof 2019-05-10 03:37:43 UTC Flags needinfo?(sbradley)
Shane Bradley 2019-05-17 15:19:36 UTC Flags needinfo?(sbradley)
Andrew Beekhof 2019-05-28 03:57:23 UTC Blocks 1703946
Luca Miccini 2019-05-28 12:34:10 UTC CC lmiccini
Ken Gaillot 2019-06-03 22:30:25 UTC Priority medium high
Status NEW ASSIGNED
Target Release --- 7.8
Target Milestone rc pre-dev-freeze
Ken Gaillot 2019-06-14 19:45:57 UTC Status ASSIGNED POST
Flags needinfo?(sbradley)
Yadnesh Kulkarni 2019-06-17 07:02:12 UTC CC ykulkarn
Shane Bradley 2019-06-17 13:44:15 UTC Flags needinfo?(sbradley)
Ken Gaillot 2019-06-17 14:47:08 UTC Blocks 1721198
Shane Bradley 2019-06-17 15:47:38 UTC Priority high urgent
Severity medium urgent
Romana Cadova 2019-06-18 08:10:48 UTC CC pkomarov
CC rcadova
Anthony Herr 2019-06-18 22:40:54 UTC CC aherr
Takashi Kajinami 2019-06-20 23:45:57 UTC CC tkajinam
Ken Gaillot 2019-06-21 00:23:54 UTC Flags needinfo?(rcadova)
Takashi Kajinami 2019-07-04 01:13:06 UTC CC kgaillot
Flags needinfo?(kgaillot)
Ken Gaillot 2019-07-05 14:21:22 UTC Flags needinfo?(rcadova) needinfo?(kgaillot)
John Ruemker 2019-07-11 15:09:10 UTC CC jruemker
Chris Feist 2019-07-15 13:45:48 UTC CC cfeist
Blocks 1729984
RAD team bot copy to z-stream 2019-07-23 07:50:56 UTC Status POST VERIFIED
QA Contact cluster-qe pkomarov
Blocks 1732335
RAD team bot copy to z-stream 2019-07-23 07:51:06 UTC Keywords ZStream
Flags blocker+
Ken Gaillot 2019-07-23 17:34:17 UTC Status VERIFIED POST
CC ctowsley
Ken Gaillot 2019-08-01 17:29:09 UTC Status POST MODIFIED
Fixed In Version pacemaker-1.1.21-1.el7
Doc Text Cause: Pacemaker implicitly ordered all stops needed on a Pacemaker Remote node before the stop of the node's Pacemaker Remote connection, including stops that were implied by fencing of the node. Also, Pacemaker scheduled actions on Pacemaker Remote nodes with a failed connection so that the actions could be done once the connection is recovered, even if the connection wasn't being recovered (for example, if the node was shutting down when the failure occurred).

Consequence: If a Pacemaker Remote node needed to be fenced while it was in the process of shutting down, once the fencing completed pacemaker scheduled probes on the node. The probes fail because the connection is not actually active. Due to the failed probe, a stop is scheduled which also fails, leading to fencing of the node again, and the situation repeats itself indefinitely.

Fix: Pacemaker Remote connection stops are no longer ordered after implied stops, and actions are not scheduled on Pacemaker Remote nodes when the connection is failed and not being started again.

Result: A Pacemaker Remote node that needs to be fenced while it is in the process of shutting down is fenced once, without repeating indefinitely.
Doc Type If docs needed, set a value Bug Fix
errata-xmlrpc 2019-08-09 21:16:10 UTC Status MODIFIED ON_QA
Patrik Hagara 2020-03-27 09:39:35 UTC Status ON_QA VERIFIED
CC phagara
errata-xmlrpc 2020-03-31 00:17:03 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2020-03-31 19:41:51 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2020-03-31 19:41:51 UTC
errata-xmlrpc 2020-03-31 19:42:36 UTC Link ID Red Hat Product Errata RHBA-2020:1032
RHEL Program Management 2020-09-20 12:22:29 UTC Flags needinfo?(kgaillot)
xiaoxwan 2020-09-21 08:26:30 UTC Flags needinfo?(kgaillot)

Back to bug 1704870