<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 4, 2024 at 5:03 AM Artur Novik <<a href="mailto:freishutz@gmail.com">freishutz@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<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>[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>for</span> i in 1 2 3 4 5 6 7; <span>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>for</span> i in 1 2 3 4 5 6 7; <span>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:rgb(0,0,0);background-color:rgb(255,255,255)">[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>
<tbody>
<tr>
<th>Pacemaker version</th>
<th>Status</th>
</tr>
<tr>
<td>2.1.5 (8.8)</td>
<td>OK</td>
</tr>
<tr>
<td>2.1.6 (8.9)</td>
<td>OK</td>
</tr>
<tr>
<td>2.1.7 (8.10)</td>
<td>Broken</td>
</tr>
<tr>
<td>2.1.8-RC2 (upstream)</td>
<td>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></div></blockquote><div><br></div><div>Hi, thanks for the report. I can try to reproduce on 2.1.8 later, but so far I'm unable to reproduce on the current upstream main branch. I don't believe there are any major differences in the relevant code between main and 2.1.8-rc2.</div><div><br></div><div>I wonder if it's an issue where the controller is busy with a synchronous request when you run `crm_node -i` (which would be a bug). Can you share logs and your config?<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Thanks,<br>
A<br>
</p>
</div>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>Regards,<br><br></div>Reid Wahl (He/Him)<br></div><div>Senior Software Engineer, Red Hat<br></div>RHEL High Availability - Pacemaker<br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>