File 0002-Test-CTS-ignore-monitor-failures-when-testing-remote.patch of Package pacemaker.15719

From 161684ee4acaac791a99fe8d5db8d0e814e20aab Mon Sep 17 00:00:00 2001
From: Ken Gaillot <kgaillot@redhat.com>
Date: Mon, 10 Dec 2018 16:40:16 -0600
Subject: [PATCH 2/2] Test: CTS: ignore monitor failures when testing remote
 node fencing

When the RemoteStonithd test killed the remote daemon, the loss was detected
via lrmd_tls_dispatch(), so nothing was done with the recurring monitors behind
the connection (which is a questionable situation).

Now that it freezes the daemon, the connection timeout is detected via
lrmd_event_disconnect(), and the monitors behind the connection are immediately
failed. Ignore those failures.
---
 cts/CTStests.py | 1 +
 1 file changed, 1 insertion(+)

Index: pacemaker-1.1.18+20180430.b12c320f5/cts/CTStests.py
===================================================================
--- pacemaker-1.1.18+20180430.b12c320f5.orig/cts/CTStests.py
+++ pacemaker-1.1.18+20180430.b12c320f5/cts/CTStests.py
@@ -3050,6 +3050,7 @@ class RemoteStonithd(RemoteDriver):
             r"pengine.*:\s+Recover remote-.*\s*\(.*\)",
             r"Calculated [Tt]ransition .*pe-error",
             r"error.*: Resource .*ocf::.* is active on 2 nodes attempting recovery",
+            r"error: Result of monitor operation for .* on remote-.*: Error",
         ]
 
         ignore_pats.extend(RemoteDriver.errorstoignore(self))