Description of problem:
OVS consuming more than 100% CPU on a Controller node (no VMs installed, only Openstack's main services).
ovs-vswitched.log shows messages like this:
~~~
2016-12-02T09:15:52.918Z|1344029|poll_loop|INFO|Dropped 143113 log messages in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
2016-12-02T09:15:52.918Z|1344030|poll_loop|INFO|wakeup due to 0-ms timeout at ofproto/bond.c:670 (100% CPU usage)
~~~
From this discussion, which describes exact issue. It is fixed in OpenVswitch 2.4.1
https://mail.openvswitch.org/pipermail/ovs-discuss/2016-July/042105.html
Version-Release number of selected component (if applicable):
Installed version:
~~~
openstack-neutron-openvswitch-2014.1.5-14.el7ost.noarch Thu Sep 8 09:56:24 2016 1473321384 Red Hat, Inc. x86-030.build.eng.bos.redhat.com
openvswitch-2.4.0-2.el7_2.x86_64 Thu Sep 8 09:55:03 2016 1473321303 Red Hat, Inc. x86-024.build.eng.bos.redhat.com
~~~
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0534.html