This task is tracking the test case writing activities to cover the bug described below.

 Problem Description: Clearly explain the issue.

During a seven day memory_leak_soak test, a memory leak soak was detected in the ovs-vswitchd daemon.

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

Memory leak over an extended period could cause more sever problems.

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

Beaker job link: https://beaker.engineering.redhat.com/jobs/12178548

RHEL-10.1-updates-20260107.3, kernel-6.12.0-124.21.1.el10_1

OVS Packages:
openvswitch-selinux-extra-policy-1.0-39.el10fdp.noarch
openvswitch3.6-3.6.1-2.el10fdp.x86_64
openvswitch3.6-debuginfo-3.6.1-2.el10fdp.x86_64

OVN Packages:
ovn25.09-25.09.1-25.el10fdp.x86_64
ovn25.09-central-25.09.1-25.el10fdp.x86_64
ovn25.09-host-25.09.1-25.el10fdp.x86_64
ovn25.09-debuginfo-25.09.1-25.el10fdp.x86_64
ovn25.09-central-debuginfo-25.09.1-25.el10fdp.x86_64
ovn25.09-host-debuginfo-25.09.1-25.el10fdp.x86_64

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

Appears to be a new issue detected in openvswitch3.6.  It was not detected in openvswitch3.5.

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

Difficult to say since the test takes so long to run.

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

Run long term memory_leak_soak test which runs iperf3 traffic constantly while adding flows every 24 hours (1K, 5K, 10K, 25K, 100K, 1M flows)

 Expected Behavior: Describe what should happen under normal circumstances.

No memory leak should be detected

 Observed Behavior: Explain what actually happens.

Memory leak is detected.

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

Had Claude perfom an analysis of the Valgrind log.  Sent log file and analysis info to @mkp who confirmed that this appears to be a real memory leak.

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

Valgrind log: http://netqe-infra01.knqe.eng.rdu2.dc.redhat.com/share/valgrind_logs/ovs-vswitchd.valgrind.log.45147

Claude analysis: http://netqe-infra01.knqe.eng.rdu2.dc.redhat.com/share/valgrind_logs/ovs_vswitchd_valgrind_analysis_45147.md