Public bug reported:

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.

The fix seems to be fixed in pacemaker-1.1.21-1.el7

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1704870

** Affects: pacemaker (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890491

Title:
  A pacemaker node fails monitor (probe) and stop /start operations on a
  resource because it returns "rc=189

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1890491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to