Bug 1985033 - [OVN] [cluster network operator] Provide the option to configure probe intervals
Summary: [OVN] [cluster network operator] Provide the option to configure probe inter...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: ffernand
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-22 17:01 UTC by Numan Siddique
Modified: 2021-10-18 17:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:40:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1165 0 None open Bug 1985033: Make inactivity_probe configurable 2021-07-27 01:19:21 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:41:03 UTC

Description Numan Siddique 2021-07-22 17:01:36 UTC
Description of problem:

cluster network operator for OVN networking should provide the option to configure the inactivity probe interval.  Right now it is hard coded to 60 seconds [1].  In scaled environments, sometimes it is desired to increase this timeout as a work around if ovsdb-server/ovn-controller keeps dropping the connection if either ovsdb-server or ovn-controller takes more than 60 seconds in one single loop.

Crazy as it may sound, ovn-controller can take > 60 seconds to complet the logical flow to openflow translation if there are lot of network policies and logical flows.

[1] - https://github.com/openshift/cluster-network-operator/blob/release-4.9/bindata/network/ovn-kubernetes/ovnkube-master.yaml#L253


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 11 errata-xmlrpc 2021-10-18 17:40:51 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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://access.redhat.com/errata/RHSA-2021:3759


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