Description of problem:

Two UDN cannot be accessed by default,  However after BGP advertised to default VRF, they will be no isolated. 

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

How reproducible:

Steps to Reproduce:

1.  Create two UDN A and B with different subnets

2.  Create RA to advertise the UDNs

oot@openshift-qe-045 bgp]# ip route | grep bgp 
10.128.0.0/23 nhid 3936 via 192.168.111.20 dev corebm proto bgp metric 20 
10.128.2.0/23 nhid 3941 via 192.168.111.23 dev corebm proto bgp metric 20 
10.129.0.0/23 nhid 3937 via 192.168.111.21 dev corebm proto bgp metric 20 
10.129.2.0/23 nhid 3933 via 192.168.111.25 dev corebm proto bgp metric 20 
10.130.0.0/23 nhid 3940 via 192.168.111.22 dev corebm proto bgp metric 20 
10.131.0.0/23 nhid 3943 via 192.168.111.24 dev corebm proto bgp metric 20 
40.100.0.0/24 nhid 3937 via 192.168.111.21 dev corebm proto bgp metric 20 
40.100.1.0/24 nhid 3941 via 192.168.111.23 dev corebm proto bgp metric 20 
40.100.2.0/24 nhid 3933 via 192.168.111.25 dev corebm proto bgp metric 20 
40.100.3.0/24 nhid 3936 via 192.168.111.20 dev corebm proto bgp metric 20 
40.100.4.0/24 nhid 3943 via 192.168.111.24 dev corebm proto bgp metric 20 
40.100.5.0/24 nhid 3940 via 192.168.111.22 dev corebm proto bgp metric 20 
50.100.0.0/24 nhid 3941 via 192.168.111.23 dev corebm proto bgp metric 20 
50.100.1.0/24 nhid 3936 via 192.168.111.20 dev corebm proto bgp metric 20 
50.100.2.0/24 nhid 3940 via 192.168.111.22 dev corebm proto bgp metric 20 
50.100.3.0/24 nhid 3943 via 192.168.111.24 dev corebm proto bgp metric 20 
50.100.4.0/24 nhid 3933 via 192.168.111.25 dev corebm proto bgp metric 20 
50.100.5.0/24 nhid 3937 via 192.168.111.21 dev corebm proto bgp metric 20 

3.   check from one namespace z9 to another namespance z8

# oc rsh -n z8 test-rc-fxccc ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if154: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default 
    link/ether 0a:58:0a:83:00:1b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.131.0.27/23 brd 10.131.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fd01:0:0:3::1b/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::858:aff:fe83:1b/64 scope link 
       valid_lft forever preferred_lft forever
3: ovn-udn1@if155: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1300 qdisc noqueue state UP group default 
    link/ether 0a:58:32:64:03:05 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 50.100.3.5/24 brd 50.100.3.255 scope global ovn-udn1
       valid_lft forever preferred_lft forever
    inet6 fe80::858:32ff:fe64:305/64 scope link 
       valid_lft forever preferred_lft forever


# oc rsh -n z9 test-rc-ncfg7 curl 50.100.3.5:8080
Hello OpenShift!

Actual results:

Expected results:

step 3 should not be able to accessed 

Additional info:

UDN to podip can be accessed,  

UDN to service ip cannot be accessed. 

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