<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi everybody,<br>
I faced with a strange behavior and I since there was a lot of
activity around crm_node structs in 2.1.7, I want to believe that
it's a regression rather than a new behavior by default.</p>
<p>"crm_node -i" occasionally, but very often, returns "<b>exit code
68</b> : <span style="font-family:monospace">Node is not known
to cluster".</span></p>
<p>The quick test below (taken from two different clusters with
pacemaker 2.1.7 and 2.1.8):</p>
<p>```</p>
<pre class="code-java">[root@node1 ~]# crm_node -i
Node is not known to cluster
[root@node1 ~]# crm_node -i
1
[root@node1 ~]# crm_node -i
1
[root@node1 ~]# crm_node -i
Node is not known to cluster
[root@node1 ~]# <span class="code-keyword">for</span> i in 1 2 3 4 5 6 7; <span
class="code-keyword">do</span> ssh node$i crm_node -i; done
1
2
Node is not known to cluster
Node is not known to cluster
5
Node is not known to cluster
7
[root@node1 ~]# <span class="code-keyword">for</span> i in 1 2 3 4 5 6 7; <span
class="code-keyword">do</span> sleep 1; ssh node$i crm_node -i ; done
Node is not known to cluster
Node is not known to cluster
Node is not known to cluster
Node is not known to cluster
Node is not known to cluster
6
7</pre>
<p></p>
<p><br>
</p>
<p><span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">[root@es-brick2
~]# crm_node -i
</span><br>
2
<br>
[root@es-brick2 ~]# crm_node -i
<br>
2
<br>
[root@es-brick2 ~]# crm_node -i
<br>
Node is not known to cluster
<br>
[root@es-brick2 ~]# crm_node -i
<br>
2
<br>
[root@es-brick2 ~]# rpm -qa | grep pacemaker | sort
<br>
pacemaker-2.1.8.rc2-1.el8_10.x86_64
<br>
pacemaker-cli-2.1.8.rc2-1.el8_10.x86_64
<br>
pacemaker-cluster-libs-2.1.8.rc2-1.el8_10.x86_64
<br>
pacemaker-libs-2.1.8.rc2-1.el8_10.x86_64
<br>
pacemaker-remote-2.1.8.rc2-1.el8_10.x86_64
<br>
pacemaker-schemas-2.1.8.rc2-1.el8_10.noarch<br>
<br>
```<br>
</span></p>
<p>I checked next versions (all packages, except the last one, taken
from rocky linux and rebuilt against corosync 3.1.8 from rocky
8.10. The distro itself rockylinux 8.10 too):</p>
<table class="confluenceTable">
<tbody>
<tr>
<th class="confluenceTh">Pacemaker version</th>
<th class="confluenceTh">Status</th>
</tr>
<tr>
<td class="confluenceTd">2.1.5 (8.8)</td>
<td class="confluenceTd">OK</td>
</tr>
<tr>
<td class="confluenceTd">2.1.6 (8.9)</td>
<td class="confluenceTd">OK</td>
</tr>
<tr>
<td class="confluenceTd">2.1.7 (8.10)</td>
<td class="confluenceTd">Broken</td>
</tr>
<tr>
<td class="confluenceTd">2.1.8-RC2 (upstream)</td>
<td class="confluenceTd">Broken</td>
</tr>
</tbody>
</table>
<p>I don't attach logs for now since I believe it could be
reproduced absolutely on any installation.</p>
<p>Thanks,<br>
A<br>
</p>
</body>
</html>