Comment 7 for bug 1896223

$ ./CTSlab.py --nodes "groovy01 groovy02 groovy03" --once --no-loop-tests --no-unsafe-tests --outputfile ~/cts.log
Sep 24 04:40:29 >>>>>>>>>>>>>>>> BEGINNING 15 TESTS
Sep 24 04:40:29 Stack: corosync 2+ (crm-corosync)
Sep 24 04:40:29 Schema: pacemaker-3.0
Sep 24 04:40:29 Scenario: Every Test Once
Sep 24 04:40:29 CTS Master: 10.250.97.104
Sep 24 04:40:29 CTS Logfile: /home/rafaeldtinoco/cts.log
Sep 24 04:40:29 Random Seed: 1600922428
Sep 24 04:40:29 Syslog variant: rsyslog
Sep 24 04:40:29 System log files: /var/log/messages
Sep 24 04:40:29 Cluster starts at boot: 1
Sep 24 04:40:29 Cluster nodes:
Sep 24 04:40:29 * groovy01
Sep 24 04:40:29 * groovy02
Sep 24 04:40:29 * groovy03
Sep 24 04:40:32 Writing log with key: 02c86ca5-acb3-4498-bfa6-726a53b23da6
Sep 24 04:40:32 Testing for combined syslog logs
Sep 24 04:40:38 Testing for journal logs
Sep 24 04:40:39 Continuing with journal-based log reader
Sep 24 04:40:45 Stopping crm-corosync on node groovy01
Sep 24 04:40:50 Stopping crm-corosync on node groovy02
Sep 24 04:40:55 Stopping crm-corosync on node groovy03
Sep 24 04:40:57 Starting Cluster Manager on all nodes.
Sep 24 04:40:59 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy02
Sep 24 04:41:29 Starting crm-corosync on node groovy03
Sep 24 04:41:50 Running test Flip (groovy03) [ 1]
Sep 24 04:42:34 Running test Restart (groovy01) [ 2]
Sep 24 04:43:00 Running test Stonithd (groovy03) [ 3]
Sep 24 04:44:07 Running test StartOnebyOne (groovy03) [ 4]
Sep 24 04:46:29 Running test SimulStart (groovy02) [ 5]
Sep 24 04:47:23 Running test SimulStop (groovy03) [ 6]
Sep 24 04:47:39 Running test StopOnebyOne (groovy03) [ 7]
Sep 24 04:48:44 Running test RestartOnebyOne (groovy02) [ 8]
Sep 24 04:50:23 Running test PartialStart (groovy03) [ 9]
Sep 24 04:51:08 Running test Standby (groovy02) [ 10]
Sep 24 04:52:03 Running test MaintenanceMode (groovy01) [ 11]
Sep 24 04:52:26 Running test ResourceRecover (groovy03) [ 12]
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Test ResourceRecover FAILED: fence-groovy01 was not recovered and is inactive
Sep 24 04:52:41 Running test Reattach (groovy03) [ 13]
Sep 24 04:54:03 Running test SpecialTest1 (groovy02) [ 14]
Sep 24 04:55:05 Running test NearQuorumPoint (groovy02) [ 15]
Sep 24 04:55:20 Stopping Cluster Manager on all nodes
Sep 24 04:55:20 Stopping crm-corosync on node groovy03
Sep 24 04:55:28 ****************
Sep 24 04:55:28 Overall Results:{'success': 14, 'failure': 1, 'BadNews': 0, 'skipped': 0}
Sep 24 04:55:28 ****************
Sep 24 04:55:28 Test Summary
Sep 24 04:55:28 Test Flip: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test Restart: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test Stonithd: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test StartOnebyOne: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test SimulStart: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test SimulStop: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test StopOnebyOne: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test RestartOnebyOne: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test PartialStart: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test Standby: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test MaintenanceMode: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test ResourceRecover: {'calls': 1, 'failure': 1, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test Reattach: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test SpecialTest1: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 Test NearQuorumPoint: {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28 <<<<<<<<<<<<<<<< TESTS COMPLETED

The test that fails does it because we have a debian patch removing
"cts-exec-helper" from the Debian package. This is part of creating the
pacemaker-cts package in order to have full regression tests before releases.

It's all good with this new merge.