Description of problem: [BGP EIP] when applying RA with nodeSelector, if PodNetwork is also listed under advertisements spec, an error should be given to reject the RA instead of accepting the RA

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

How reproducible:

Steps to Reproduce:

1. with default network advertised, I accidentally applied a second RA with a nodeSelector but with both PodNetwork and EgressIP listed under advertisements spec

#cat ra-eip-nodeselector.yaml 
apiVersion: k8s.ovn.org/v1
kind: RouteAdvertisements
metadata:
  name: ra-eip-nodeselector 
apec:
  nodeSelector:
    matchLabels:
      k8s.ovn.org/egress-assignable: true
  networkSelector:
    matchLabels:
      k8s.ovn.org/default-network: ""
  advertisements:
  - "PodNetwork"
  - "EgressIP"

2.  The RA was accepted without any error

#oc get ra -A
NAME                  STATUS
default               Accepted
ra-eip-nodeselector   Accepted

#oc get ra ra-eip-nodeselector -oyaml
apiVersion: k8s.ovn.org/v1
kind: RouteAdvertisements
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apec":{"advertisements":["PodNetwork","EgressIP"],"networkSelector":{"matchLabels":{"k8s.ovn.org/default-network":""}},"nodeSelector":{"matchLabels":

}},"apiVersion":"k8s.ovn.org/v1","kind":"RouteAdvertisements","metadata":{"annotations":{},"name":"ra-eip-nodeselector"}}
  creationTimestamp: "2025-03-13T17:06:39Z"
  generation: 1
  name: ra-eip-nodeselector
  resourceVersion: "1052294"
  uid: 9a5c6c3d-c78d-4784-91fc-579b87a61ed6
status:
  conditions:
  - lastTransitionTime: "2025-03-13T17:06:40Z"
    message: ovn-kubernetes cluster-manager validated the resource and requested the
      necessary configuration changes
    observedGeneration: 1
    reason: Accepted
    status: "True"
    type: Accepted
  status: Accepted

3.

Actual results:  the second RA was accepted without any error

Expected results:  the second RA should be rejected as nodeSelector is currently not supported for PodNetwork

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:

• 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