On Tue, May 21, 2019 at 11:12:48AM -0400, Jamon Camisso wrote:
> On 07/05/2019 09:43, Jamon Camisso wrote:
> > Following up on this since it is still an issue.
>
> For future travelers: the cloud where I was working on this was upgraded
> to use Stein, which brings with it openvswitch-switch
On 07/05/2019 09:43, Jamon Camisso wrote:
> Following up on this since it is still an issue.
For future travelers: the cloud where I was working on this was upgraded
to use Stein, which brings with it openvswitch-switch 2.11.0. The issue
appears to be resolved in that version.
Cheers, Jamon
Following up on this since it is still an issue.
strace on the thread in question shows the following:
13:35:47 poll([{fd=23, events=POLLIN}], 1, 0) = 0 (Timeout) <0.18>
13:35:47 epoll_wait(42, [{EPOLLIN, {u32=3, u64=3}}], 9, 0) = 1 <0.18>
13:35:47 recvmsg(417, {msg_namelen=0},
I'm seeing an identical issue to the one posted here a few months ago:
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-October/047558.html
- I'll include the bug report template at the end.
The issue is an ovs-vswitchd thread consuming 100% CPU in a very lightly
used Openstack Rocky
