Bug 1401379

Summary: Backport openvswitch version 2.4.1
Product: Red Hat OpenStack Reporter: Sachin <sacpatil>
Component: openvswitchAssignee: Assaf Muller <amuller>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: urgent Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: aloughla, amuller, apevec, astafeye, ccollett, chrisw, dcadzow, ealcaniz, fleitner, jjoyce, lhh, mburns, mschuppe, oblaut, pablo.iranzo, rhos-maint, srevivo
Target Milestone: asyncKeywords: FeatureBackport, ZStream
Target Release: 5.0 (RHEL 7)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openvswitch-2.4.1-1.git20160727.el7_2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1426320 (view as bug list) Environment:
Last Closed: 2017-03-15 13:01:53 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:
Bug Depends On:    
Bug Blocks: 1426320    

Description Sachin 2016-12-05 05:09:17 UTC 
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:
Comment 6 Sachin 2017-02-10 04:30:21 UTC 
Can we have urgent hot-fix?. Customer have asked for ETA for hot-fix
Comment 30 errata-xmlrpc 2017-03-15 13:01:53 UTC 
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