Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-1049

arp reply is not sent for lb on lr added through template

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • None
    • ovn24.09
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • rhel-9
    • rhel-sst-network-fastdatapath-ovn
    • ssg_networking

       Problem Description: Clearly explain the issue.

      when a lb is added to lr through template, the arp reply is not sent for the lb vip

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

       

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

      ovn24.09-24.09.1-10.el9fdp.x86_64
      ovn24.09-central-24.09.1-10.el9fdp.x86_64
      ovn24.09-host-24.09.1-10.el9fdp.x86_64
      openvswitch3.3-3.3.0-58.el9fdp.x86_64

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

       

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

      100%

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

      systemctl start openvswitch                          
      systemctl start ovn-northd                                                                            
      ovn-nbctl set-connection ptcp:6641                                                                    
      ovn-sbctl set-connection ptcp:6642
      ovs-vsctl set open . external_ids:system-id=hv1 external_ids:ovn-remote=tcp:127.0.0.1:6642 external_ids:ovn-encap-type=geneve external_ids:ovn-encap-ip=127.0.0.1
      systemctl restart ovn-controllerovs-vsctl add-br br-ext
      ovs-vsctl set Open_vSwitch . external-ids:ovn-bridge-mappings=phynet:br-extovn-nbctl lr-add lr1
      ovn-nbctl lrp-add lr1 lr1-ls1 00:00:01:ff:02:03 192.168.1.254/24ovn-nbctl ls-add ls1
      ovn-nbctl lsp-add ls1 ls1p1
      ovn-nbctl lsp-set-addresses ls1p1 "00:00:01:01:01:01 192.168.1.1"ovn-nbctl lsp-add ls1 ls1-lr1
      ovn-nbctl lsp-set-type ls1-lr1 router
      ovn-nbctl lsp-set-options ls1-lr1 router-port=lr1-ls1
      ovn-nbctl lsp-set-addresses ls1-lr1 routerovn-nbctl ls-add pub
      ovn-nbctl lrp-add lr1 lr1-pub 00:00:01:ff:01:03 172.16.1.1/24ovn-nbctl lsp-add pub pub-lr1
      ovn-nbctl lsp-set-type pub-lr1 router
      ovn-nbctl lsp-set-addresses pub-lr1 router
      ovn-nbctl lsp-set-options pub-lr1 router-port=lr1-pubovn-nbctl lsp-add pub pub-ln
      ovn-nbctl lsp-set-type pub-ln localnet
      ovn-nbctl lsp-set-addresses pub-ln unknown
      ovn-nbctl lsp-set-options pub-ln network_name=phynet
      ovn-nbctl set logical_router lr1 options:chassis=hv1ovn-nbctl create chassis_template_var chassis=hv1 \
          variables="{lbvip=172.16.1.100,lbport=12010,lbback=192.168.1.1}"
      ovn-nbctl --template lb-add lb1 "^lbvip:^lbport" "^lbback:^lbport" tcp ipv4
      ovn-nbctl lr-lb-add lr1 lb1ovs-vsctl add-port br-int ls1p1 -- set interface ls1p1 type=internal external_ids:iface-id=ls1p1
      ip netns add ls1p1
      ip link set ls1p1 netns ls1p1
      ip netns exec ls1p1 ip link set ls1p1 address 00:00:01:01:01:01
      ip netns exec ls1p1 ip link set ls1p1 up
      ip netns exec ls1p1 ip addr add 192.168.1.1/24 dev ls1p1
      ip netns exec ls1p1 ip route add default via 192.168.1.254
      ip netns exec ls1p1 ncat -k -l 12010 &ovs-vsctl add-port br-ext ext1 -- set interface ext1 type=internal
      ip netns add ext1
      ip link set ext1 netns ext1
      ip netns exec ext1 ip link set ext1 up
      ip netns exec ext1 ip addr add 172.16.1.11/24 dev ext1
      ovn-nbctl --wait=hv syncip netns exec ext1 ping 172.16.1.1 -c 1
      ip netns exec ext1 ncat 172.16.1.100 12010 <<< h
      ip netns exec ext1 ip neigh
      ip netns exec ext1 ip neigh flush all
      ip netns exec ext1 ip neigh add 172.16.1.100 dev ext1 lladdr 00:00:01:ff:01:03ip netns exec ext1 ncat 172.16.1.100 12010 <<< h 

       Expected Behavior: Describe what should happen under normal circumstances.

      ncat to lb should pass

       Observed Behavior: Explain what actually happens.

      ncat to lb failed, arp table is not installed for the lb vip

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

       

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

       

      + ip netns exec ls1p1 ncat -k -l 12010
      + ip netns add ext1
      + ip link set ext1 netns ext1                                                                         
      + ip netns exec ext1 ip link set ext1 up                                                              
      + ip netns exec ext1 ip addr add 172.16.1.11/24 dev ext1                                              
      + ovn-nbctl --wait=hv sync                                                                            
      + ip netns exec ext1 ping 172.16.1.1 -c 1                                                             
      PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.                                                    
      64 bytes from 172.16.1.1: icmp_seq=1 ttl=254 time=5.79 ms                                             --- 172.16.1.1 ping statistics ---                                                                    
      1 packets transmitted, 1 received, 0% packet loss, time 0ms                                           
      rtt min/avg/max/mdev = 5.792/5.792/5.792/0.000 ms
      + ip netns exec ext1 ncat 172.16.1.100 12010
      Ncat: TIMEOUT.
      
      <=== ncat failed 
      
      + ip netns exec ext1 ip neigh                                                                         
      172.16.1.1 dev ext1 lladdr 00:00:01:ff:01:03 REACHABLE 
      172.16.1.100 dev ext1 INCOMPLETE 
      + ip netns exec ext1 ip neigh flush all                                                               
      + ip netns exec ext1 ip neigh add 172.16.1.100 dev ext1 lladdr 00:00:01:ff:01:03                      
      + ip netns exec ext1 ncat 172.16.1.100 12010                                                          
      h 
      
      <== ncat passed after neigh is added manually 

              ovnteam@redhat.com OVN Team
              rhn-support-jishi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: