Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1770295

Summary: ovn-controller consumes to much memory and eventually core dumps
Product: Red Hat Enterprise Linux Fast Datapath Reporter: David Hill <dhill>
Component: ovn2.11Assignee: OVN Team <ovnteam>
Status: CLOSED DUPLICATE QA Contact: Jianlin Shi <jishi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: FDB 18.11CC: apevec, ctrautma, dalvarez, dceara, ffernand, fhallal, lhh, majopela, nusiddiq, rkhan, scohen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1770953 (view as bug list) Environment:
Last Closed: 2020-04-07 08:32:17 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1770953    

Description David Hill 2019-11-08 16:30:30 UTC 
Description of problem:
ovn-controller consumes to much memory and eventually core dumps

Version-Release number of selected component (if applicable):
ovn2.11-central-2.11.1-0.el7fdn.x86_64
rhosp-openvswitch-ovn-host-2.11-0.1.el7ost.noarch
rhosp-openvswitch-ovn-common-2.11-0.1.el7ost.noarch
puppet-ovn-12.4.0-2.el7ost.noarch
ovn2.11-2.11.1-0.el7fdn.x86_64
ovn2.11-host-2.11.1-0.el7fdn.x86_64
rhosp-openvswitch-ovn-central-2.11-0.1.el7ost.noarch


How reproducible:
This environment

Steps to Reproduce:
1. Let it sit for a while
2.
3.

Actual results:
ctl01 ovn_controller memory consumption is at 39.27G.
ctl02 ovn_controller memory consumption is at 27.72G.
ctl03 ovn_controller memory consumption is at 19.87G.

Expected results:


Additional info:
Comment 22 Numan Siddique 2020-04-07 08:32:17 UTC 

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