<div dir="ltr"><div dir="ltr">I'm seeing identical behavior on a second system. Has anyone else experienced this?<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 20, 2019 at 10:58 PM Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com">lars@redhat.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"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 20, 2019 at 10:13 PM Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com" target="_blank">lars@redhat.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">I was trying to track down some connectivity issues with some<br>
baremetal nodes booting from iSCSI LUNs provided by Cinder. It turns<br>
out that openvswitch is going belly-up. We see in<br>
openvswitch-agent.log a "Switch connection timeout" error [1]. Just<br>
before that, in /var/log/openvswitch/ovs-vswitchd.log, we see:<br>
<br>
2019-02-21T00:32:38.696Z|00795|bridge|INFO|bridge br-tun: deleted interface patch-int on port 1<br>
2019-02-21T00:32:38.696Z|00796|bridge|INFO|bridge br-tun: deleted interface br-tun on port 65534<br>
2019-02-21T00:32:38.823Z|00797|bridge|INFO|bridge br-int: deleted interface int-br-ctlplane on port 1<br>
2019-02-21T00:32:38.823Z|00798|bridge|INFO|bridge br-int: deleted interface br-int on port 65534<br>
2019-02-21T00:32:38.823Z|00799|bridge|INFO|bridge br-int: deleted interface tapb0101920-b9 on port 4<br>
2019-02-21T00:32:38.824Z|00800|bridge|INFO|bridge br-int: deleted interface patch-tun on port 3<br>
2019-02-21T00:32:38.954Z|00801|bridge|INFO|bridge br-ctlplane: deleted interface phy-br-ctlplane on port 4<br>
2019-02-21T00:32:38.954Z|00802|bridge|INFO|bridge br-ctlplane: deleted interface br-ctlplane on port 65534<br>
2019-02-21T00:32:38.954Z|00803|bridge|INFO|bridge br-ctlplane: deleted interface em2 on port 3<br></blockquote><div></div><div><br></div><div><div dir="ltr"><div>The plot thickens: it looks as if something may be doing this explicitly? At the same time, we see in the system journal:</div><div><br></div><div></div><div>Thu 2019-02-21 00:32:38.697531 UTC [s=fa1c368ed0314169b286a29ffe7d9f87;i=4aa2b;b=d64947ee218546d8a94103aa9bbee154;m=4b31e6780;t=5825c9c8dda3b;x=13507b4516ddcb27]<br> _TRANSPORT=stdout<br> PRIORITY=6<br> SYSLOG_FACILITY=3<br> _UID=0<br> _GID=0<br> _CAP_EFFECTIVE=1fffffffff<br> _SELINUX_CONTEXT=system_u:system_r:init_t:s0<br> _BOOT_ID=d64947ee218546d8a94103aa9bbee154<br> _MACHINE_ID=4a470fefdd3b4033a163bb69bc8578da<br> _HOSTNAME=localhost.localdomain<br> _SYSTEMD_SLICE=system.slice<br> _EXE=/usr/bin/bash<br> _STREAM_ID=951219afe7fb4eb4bf5d71af983d1f11<br> SYSLOG_IDENTIFIER=ovs-ctl<br> MESSAGE=Exiting ovs-vswitchd (9340) [ OK ]<br> _PID=868225<br> _COMM=ovs-ctl<br> _CMDLINE=/bin/sh /usr/share/openvswitch/scripts/ovs-ctl --no-ovsdb-server stop<br> _SYSTEMD_CGROUP=/system.slice/ovs-vswitchd.service/control<br> _SYSTEMD_UNIT=ovs-vswitchd.service<br></div><div><br></div><div>...but there's nothing else around that time that seems relevant.<br></div><div><br></div></div><div dir="ltr">-- <br></div></div></div><div dir="ltr" class="gmail-m_5532812030725475332m_-3881719807802902546gmail_signature"><div dir="ltr">Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com" target="_blank">lars@redhat.com</a>><div><br></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Lars Kellogg-Stedman <<a href="mailto:lars@redhat.com" target="_blank">lars@redhat.com</a>><div><br></div></div></div></div>