Good finding. So it is a known kernel bug and it won't get fixed in that
kernel version. :(
>From OVS point of view, the problem is, if such bug exists in kernel, it
prevents ovs-vswitchd to be killed (even by SIGKILL) because the process is
in system call which got blocked because of the kernel bu
Hi:
Adding correct ovs-discuss ML. I did get a chance to take a look on it a
bit. I think this is the bug in 4.4.0-104-generic kernel on ubuntu 16.04 as
its being discussed on ubuntu forum
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 where it can
be hit all of a sudden as per the
Hi,
We upgrade the OVS recently from one version 2.10 to another version 2.10. on
some HV upgrade, the HV is down when running force reload kernel.
In the ovs-ctl log, kill ovs-vswitch is failed, but the script is still going
to reload the modules.
```
ovsdb-server is running with pid 2431
ovs-v
Hi,
We upgrade the OVS recently from one version 2.10 to another version 2.10. on
some HV upgrade, the HV is down when running force reload kernel.
In the ovs-ctl log, kill ovs-vswitch is failed, but the script is still going
to reload the modules.
```
ovsdb-server is running with pid 2431
ovs
Hi,
We upgrade the OVS recently from one version 2.10 to another version 2.10. on
some HV upgrade, the HV is down when running force reload kernel.
In the ovs-ctl log, kill ovs-vswitch is failed, but the script is still going
to reload the modules.
```
ovsdb-server is running with pid 2431
ovs-v
From: "Jin, Liang"
Date: Wednesday, August 28, 2019 at 3:58 AM
To: "ovs-dev@openvswitch.org"
Cc: "Zhou, Han" , "Murthy, Sudheendra(sumurthy)"
Subject: Hypervisor down during upgrade OVS 2.10.x to 2.10.y
Hi,
We upgrade the OVS recently from one version 2.10 to another version 2.10. on
some
