Description of problem:

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

How reproducible: Always

Steps to Reproduce:

1.  Enable audit logs - `base_network_controller_namespace.go:335] Namespace ext: ACL logging is set to deny=debug allow=info`

2.  oc adm top pods --containers -n openshift-ovn-kubernetes | grep ovnkube-node-XXX

3.

Actual results:  ovn-controller memory usage grows slowly over time and never garbage collects due to not being idle for 30 seconds.

~~~

oc adm top pods --containers -n openshift-ovn-kubernetes | grep ovnkube-node-XXX

—

kube-rbac-proxy-node 1m 17Mi

kube-rbac-proxy-ovn-metrics 1m 19Mi

nbdb 1m 12Mi

northd 1m 13Mi

ovn-acl-logging 3m 1Mi

ovn-controller 7m 7023Mi

ovnkube-controller 8m 122Mi

sbdb 1m 17Mi

~~~

~~~

oc logs -n openshift-ovn-kubernetes ovnkube-node-vjx88 -c ovn-controller

—

{{2025-01-12T00:09:30.558Z|01282|memory_trim|INFO|Detected inactivity (last active 30001 ms ago): trimming memory
2025-01-12T00:10:31.173Z|01283|memory_trim|INFO|Detected inactivity (last active 30000 ms ago): trimming memory
2025-01-12T01:00:43.319Z|01284|memory_trim|INFO|Detected inactivity (last active 30003 ms ago): trimming memory
2025-01-12T01:01:42.093Z|01285|memory_trim|INFO|Detected inactivity (last active 30002 ms ago): trimming memory
2025-01-12T01:10:52.516Z|01286|memory_trim|INFO|Detected inactivity (last active 30005 ms ago): trimming memory}}

~~~

Expected results:  ovn-controller  should better manage its memory usage so that the admin doesn't have to delete it preemptively.

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms:

Is it an

1. ovn-controller

If it is an internal RedHat testing failure:

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure:

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components