Description of problem: lflow-cache-limit-kb flag in ovn-kubernetes is used to determine the maximum size of the logical flow cache (in KB) ovn-controller, it is using ovn-limit-lflow-cache-kb external-ids in ovnk, but should be ovn-memlimit-lflow-cache-kb according to ovn-controller man page: https://www.ovn.org/support/dist-docs/ovn-controller.8.html Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Checked on version 4.11.0-0.nightly-2022-06-21-151125. ovn-memlimit-lflow-cache-kb is added into external-ids and ovn-limit-lflow-cache-kb is removed. % oc debug node/ip-10-0-130-174.us-east-2.compute.internal -- chroot /host ovs-vsctl get open . external-ids Starting pod/ip-10-0-130-174us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` {hostname=ip-10-0-130-174.us-east-2.compute.internal, ovn-bridge-mappings="physnet:br-ex", ovn-enable-lflow-cache="true", ovn-encap-ip="10.0.130.174", ovn-encap-type=geneve, ovn-memlimit-lflow-cache-kb="1048576", ovn-monitor-all="true", ovn-ofctrl-wait-before-clear="0", ovn-openflow-probe-interval="180", ovn-remote="ssl:10.0.130.174:9642,ssl:10.0.186.207:9642,ssl:10.0.197.5:9642", ovn-remote-probe-interval="180000", rundir="/var/run/openvswitch", system-id="48ff4ee4-176e-42a6-b4cd-e534dc7a2382"} % oc version Client Version: 4.11.0-0.nightly-2022-06-14-032134 Kustomize Version: v4.5.4 Server Version: 4.11.0-0.nightly-2022-06-21-151125 Kubernetes Version: v1.24.0+284d62a
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 (Important: OpenShift Container Platform 4.11.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-2022:5069