Bug 1401379 - Backport openvswitch version 2.4.1
Summary: Backport openvswitch version 2.4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 5.0 (RHEL 7)
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: async
: 5.0 (RHEL 7)
Assignee: Assaf Muller
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks: 1426320
TreeView+ depends on / blocked
 
Reported: 2016-12-05 05:09 UTC by Sachin
Modified: 2020-06-11 13:07 UTC (History)
17 users (show)

Fixed In Version: openvswitch-2.4.1-1.git20160727.el7_2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1426320 (view as bug list)
Environment:
Last Closed: 2017-03-15 13:01:53 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0534 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 5 Bug Fix and Enhancement Advisory 2017-03-15 17:01:28 UTC

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


Note You need to log in before you can comment on or make changes to this bug.