Description of problem:
Customer is facing issue while accessing a LB service.
The condition of failure is:

• Put 2 LB services on same node (Pod on same node).
• Service port for both the LB services should be same.
• Both the LB service should have Node Port assigned.
  One of the the two LB service in above condition is unreachable. connection using the specific node port for the affected service also does not work.
   
  when checking further we found that the node port for the affected service is not listening on the OCP nodes.
   
  Below error logs are seen in ovnkube-node pod for same node port.
  2024-10-22T13:29:28.686118923Z W1022 13:29:28.686084 3991638 port_claim.go:126] PortClaim for svc: xxxx-ccs-xxf-session/xxx-data-repository-db-cluster-2-dr on port: 35900, err: listen tcp :35900: bind: address already in use 2024-10-22T13:29:28.686156025Z I1022 13:29:28.686126 3991638 event.go:298] Event(v1.ObjectReference{Kind:"Service", Namespace:"xxxx-ccs-xxf-session", Name:"xxxf-data-repository-db-cluster-2-dr", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'PortClaim' Service: xxxxx-ccs-xxf-session/xxx-data-repository-db-cluster-2-dr requires port: 35900 to be opened on node, but port cannot be opened, err: listen tcp :35900: bind: address already in use
  Version-Release number of selected component (if applicable): OCP version 4.14.35

How reproducible: I am not able to reproduce this issue in my test cluster but this issue persist in customer environment.

Steps to Reproduce:

1. Put 2 LB services on same node (Pod on same node).

2. Service port for both the LB services should be same.

3. Both the LB service should have Node Port assigned.

4. One of the the two LB service in above condition is unreachable.

Actual results: One of the the two LB service is unreachable.

Expected results: Both LB services should be reachable.

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. internal CI failure
2. customer issue / SD
3. internal RedHat testing failure

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: Customer 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