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:
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