<html><head></head><body><div dir="auto">Chris, <br>Thanks for trying this. My experience has been with the cluster services running on VMs, when the cable to the hypervisor is pulled. The hypervisor only had one VM with cluster services on it. The remaining cluster nodes were on other VMs on other hypervisor, all on the same subnet.<br><br>I'm not sure if the nmcli command being run on the VM would reproduce the same effect? <br><br>-John<br><br><br></div><br><br><div class="gmail_quote"><div dir="auto">On September 11, 2026 4:12:43 PM EDT, Chris Lumens <clumens@redhat.com> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="com-fsck-k9__plain-text-message-pre"><blockquote class="gmail_quote" style="margin-bottom: 1ex; --com-fsck-k9__blockquote-default-border-color: #729fcf;"><div dir="auto">pacemaker 2.1.9-1 On Rhel 9.6 - No problem with network isolation<br>pacemaker 2.1.10-2 On Rhel 9.8 - Problem I described<br></div></blockquote><div dir="auto">I've been trying to reproduce this today, but so far no luck. I had an idea which patch might be to blame, so maybe there's another patch at fault that I haven't tried yet. Alternatively, perhaps there's something about how I am taking down the network on my VM (nmcli device down) that results in different behavior than how you are losing the network.<br><br>- Chris<br><br></div></pre></blockquote></div></body></html>