Last autopkgtest that succeed shows:
autopkgtest [07:14:15]: test pacemaker: [----------------------- + sleep 60 + crm_mon -1 + hostname -s + fgrep -20 Online: [ autopkgtest ] Stack: corosync Current DC: autopkgtest (version 1.1.18-2b07d5c5a9) - partition WITHOUT quorum Last updated: Tue Jul 16 07:15:15 2019 Last change: Tue Jul 16 07:14:32 2019 by hacluster via crmd on autopkgtest
1 node configured 0 resources configured
Online: [ autopkgtest ]
No active resources
autopkgtest [07:15:16]: test pacemaker: -----------------------] autopkgtest [07:15:16]: test pacemaker: - - - - - - - - - - results - - - - - - - - - - pacemaker PASS autopkgtest [07:15:16]: @@@@@@@@@@@@@@@@@@@@ summary pacemaker PASS
----
Before the upgrade, the test has also failed with similar (as now) output:
autopkgtest [20:08:18]: test pacemaker: [----------------------- + sleep 60 + crm_mon -1 + hostname -s + fgrep -20 Online: [ autopkgtest ] autopkgtest [20:09:18]: test pacemaker: -----------------------] autopkgtest [20:09:18]: test pacemaker: - - - - - - - - - - results - - - - - - - - - - pacemaker FAIL non-zero exit status 1 autopkgtest [20:09:18]: @@@@@@@@@@@@@@@@@@@@ summary pacemaker FAIL non-zero exit status 1
And after the upgrade, just one test and failed the same way:
autopkgtest [20:26:39]: test pacemaker: [----------------------- + ulimit -H -l unlimited + sleep 25 + fgrep -20 Online: [ node1 ] + crm_mon -1 autopkgtest [20:27:05]: test pacemaker: -----------------------] autopkgtest [20:27:05]: test pacemaker: - - - - - - - - - - results - - - - - - - - - - pacemaker FAIL non-zero exit status 1 autopkgtest [20:27:06]: @@@@@@@@@@@@@@@@@@@@ summary pacemaker FAIL non-zero exit status 1
Meaning, AT LEAST, the test is flakky and likely because of timing issues waiting for corosync or some other reason (can't reproduce locally).
Last autopkgtest that succeed shows:
autopkgtest [07:14:15]: test pacemaker: [------ ------- ------- ---
+ sleep 60
+ crm_mon -1
+ hostname -s
+ fgrep -20 Online: [ autopkgtest ]
Stack: corosync
Current DC: autopkgtest (version 1.1.18-2b07d5c5a9) - partition WITHOUT quorum
Last updated: Tue Jul 16 07:15:15 2019
Last change: Tue Jul 16 07:14:32 2019 by hacluster via crmd on autopkgtest
1 node configured
0 resources configured
Online: [ autopkgtest ]
No active resources
autopkgtest [07:15:16]: test pacemaker: ------- ------- ------- --] @@@@@@@ @@@@@@ summary
autopkgtest [07:15:16]: test pacemaker: - - - - - - - - - - results - - - - - - - - - -
pacemaker PASS
autopkgtest [07:15:16]: @@@@@@@
pacemaker PASS
----
Before the upgrade, the test has also failed with similar (as now) output:
autopkgtest [20:08:18]: test pacemaker: [------ ------- ------- --- ------- ------- --] @@@@@@@ @@@@@@ summary
+ sleep 60
+ crm_mon -1
+ hostname -s
+ fgrep -20 Online: [ autopkgtest ]
autopkgtest [20:09:18]: test pacemaker: -------
autopkgtest [20:09:18]: test pacemaker: - - - - - - - - - - results - - - - - - - - - -
pacemaker FAIL non-zero exit status 1
autopkgtest [20:09:18]: @@@@@@@
pacemaker FAIL non-zero exit status 1
----
And after the upgrade, just one test and failed the same way:
autopkgtest [20:26:39]: test pacemaker: [------ ------- ------- --- ------- ------- --] @@@@@@@ @@@@@@ summary
+ ulimit -H -l unlimited
+ sleep 25
+ fgrep -20 Online: [ node1 ]
+ crm_mon -1
autopkgtest [20:27:05]: test pacemaker: -------
autopkgtest [20:27:05]: test pacemaker: - - - - - - - - - - results - - - - - - - - - -
pacemaker FAIL non-zero exit status 1
autopkgtest [20:27:06]: @@@@@@@
pacemaker FAIL non-zero exit status 1
----
Meaning, AT LEAST, the test is flakky and likely because of timing issues waiting for corosync or some other reason (can't reproduce locally).