Bug 1392629

Summary: High openvswitch CPU usage
Product: Red Hat OpenStack Reporter: Jeremy <jmelvin>
Component: openvswitchAssignee: Flavio Leitner <fleitner>
Status: CLOSED DUPLICATE QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: apevec, chrisw, fleitner, jmelvin, rhos-maint, srevivo
Target Milestone: ---Keywords: Unconfirmed
Target Release: ---Flags: fleitner: needinfo? (jmelvin)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-07 20:19:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeremy 2016-11-07 22:46:13 UTC
Description of problem: The following messages filling up openvswitch logs:

/var/log/openvswitch/ovs-vswitchd.log 
2016-11-07T15:49:27.793Z|327610|poll_loop|INFO|wakeup due to 0-ms timeout at ofproto/bond.c:670 (498% CPU usage)
2016-11-07T15:49:37.137Z|327611|poll_loop|INFO|Dropped 8854 log messages in last 9 seconds (most recently, 9 seconds ago) due to excessive rate




Version-Release number of selected component (if applicable):

openstack-neutron-openvswitch-2015.1.4-2.el7ost.noarch
openvswitch-2.4.0-2.el7_2.x86_64



Additional info:

Comment 2 Jeremy 2016-11-15 17:12:33 UTC
<lrichard> jmelvin: actually, I think this is something that was fixed in upstream OVS v 2.4.1, commit 745a6929166c56bda6403d75fc1f84906388557e
<lrichard> jmelvin: https://mail.openvswitch.org/pipermail/ovs-discuss/2016-July/042105.html

Comment 3 Flavio Leitner 2017-02-21 18:56:15 UTC
OSP 7 has been updated with: openvswitch-2.5.0-14.git20160727.el7fdp.x86_64.rpm
which includes the fix.

Could you please just update it?

Comment 4 Red Hat Bugzilla Rules Engine 2017-02-21 18:56:24 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 5 Flavio Leitner 2017-03-07 20:19:32 UTC

*** This bug has been marked as a duplicate of bug 1359040 ***