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

 Problem Description: Clearly explain the issue.

Regression of https://issues.redhat.com/browse/FDP-826

Customer sees uneven tcp connection distribution on OpenShift services when the number of backing pods is not a power of 2, while it sees even distribution when the number of backing pods is a power of 2.

In what regards OVS, like in the original bug, services are implemented as OVN load balancers, which means that there are OVS groups using dp_hash selection algorithm to choose one target pod or the other.
 

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

Uneven distribution of load penalizes application performance. Workaround is not possible because automated scaling is required for the application and the autoscaler cannot be forced to choose powers of 2 only.
 

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

openvswitch3.3-3.3.4-110.el9fdp.x86_64
 

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

Regression.
 

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

Consistently reproduced at customer side.
 

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

• Have a service with a number of backing pods that is a power of 2, monitor the requests each pod receives, an even distribution of connections is seen.
• Have the same service but with a number of pods not being a power of 2, monitor the requests each pod receives, an uneven distribution of connections is seen.
   

   Expected Behavior: Describe what should happen under normal circumstances.

Even distribution regardless of whether the number of pods is a power of 2 or not.
 

 Observed Behavior: Explain what actually happens.

Explained above.
 

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

• OVN-level configuration was checked and everything was fine.
• OVS groups were checked and I could not find anything odd.
• Customer tested to have a number of pods being a power of 2 and traffic distribution became even, while at normal (with number of pod not being power of 2) it is uneven.
   

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

I'll provide this internally