This is tracking the upstream effort needed to deliver the solution to the bug described below.

 Problem Description: Clearly explain the issue.

OpenShift has witnessed a ~10% memory regression in ovn-controller and OVS after the minor version bump for OVN.

 Impact Assessment: Describe the severity and impact (e.g., network down,availability of a workaround, etc.).

Increased memory utilization

 Software Versions: Specify the exact versions in use (e.g.,openvswitch3.1-3.1.0-147.el8fdp).

ovn25.03-25.03.1-98.el9fdp

  Issue Type: Indicate whether this is a new issue or a regression (if a regression, state the last known working version).

regression over the previous release ovn25.03-25.03.1-60.el9fdp.

 Reproducibility: Confirm if the issue can be reproduced consistently. If not, describe how often it occurs.

100%

 Reproduction Steps: Provide detailed steps or scripts to replicate the issue.

imaximet@redhat.com opened a bug to revert to the older ovn version and we see the memory return to baseline – see https://github.com/openshift/ovn-kubernetes/pull/2900 

Must results showing the before and after the change and revert  are here- https://gist.github.com/jtaleric/1f95e058d69bf27da2d1b00613a1febe 

Each buildURL has the collection of mg and other artifacts in Prow.

 Expected Behavior: Describe what should happen under normal circumstances.

 Observed Behavior: Explain what actually happens.

 Troubleshooting Actions: Outline the steps taken to diagnose or resolve the issue so far.

 Logs: If you collected logs please provide them (e.g. sos report, /var/log/openvswitch/* , testpmd console)