Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-15794

[BGP EVPN] requires neutron_bgpvpn:type and vni to be manually set

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • ovn-bgp-agent
    • None
    • Important

      Steps to reproduce the behavior:

      RHOSO deployment with EPVN enabled via ovn-bgp-agent NBDB. 

      driver=nb_ovn_bgp_driver
      exposing_method=vrf
      evpn_nic=nic5
      evpn_udp_dstport=4789
      
      [zuul@controller-0 ~]$ ovn-nbctl get logical-switch 672ca1fc-f2a8-44f0-bb5d-c98a47ae8abf external_ids
      {"neutron:availability_zone_hints"="", "neutron:mtu"="9000", "neutron:network_name"=provider1, "neutron:provnet-network-type"=flat, "neutron:revision_number"="2"}
      

       

      Error log:

      Apr 14 12:32:23 compute-0 ovn_bgp_agent[177444]: 2025-04-14 12:32:23.691 2 DEBUG ovn_bgp_agent.drivers.openstack.nb_ovn_bgp_driver [-] Adding BGP route for logical port with ip ['172.16.101.125'] _expose_ip /usr/lib/python3.9/site-packages/ovn_bgp_agent/drivers/openstack/nb_ovn_bgp_driver.py:540#033[00m  
      
      Apr 14 12:32:23 compute-0 ovn_bgp_agent[177444]: 2025-04-14 12:32:23.691 2 WARNING ovn_bgp_agent.drivers.openstack.utils.wire [-] EVPN has not been setup for bridge br-ex with vlan device None. Either the network has not been configured, or something went wrong in the base wiring method.#033[00m 
      
      Apr 14 12:32:23 compute-0 ovn_bgp_agent[177444]: 2025-04-14 12:32:23.692 2 DEBUG ovn_bgp_agent.drivers.openstack.nb_ovn_bgp_driver [-] Adding BGP route for logical port with ip ['172.16.101.229'] _expose_ip /usr/lib/python3.9/site-packages/ovn_bgp_agent/drivers/openstack/nb_ovn_bgp_driver.py:540#033[00m  
      
      Apr 14 12:32:23 compute-0 ovn_bgp_agent[177444]: 2025-04-14 12:32:23.693 2 WARNING ovn_bgp_agent.drivers.openstack.utils.wire [-] EVPN has not been setup for bridge br-ex with vlan device None. Either the network has not been configured, or something went wrong in the base wiring method.#033[00m  

       

      Workaround:

      [zuul@controller-0 ~]$ ovn-nbctl set logical-switch 672ca1fc-f2a8-44f0-bb5d-c98a47ae8abf external_ids:"neutron_bgpvpn\:type"="l3"
       
      [zuul@controller-0 ~]$  ovn-nbctl set logical-switch 672ca1fc-f2a8-44f0-bb5d-c98a47ae8abf external_ids:"neutron_bgpvpn\:vni"="1001"
       
      [zuul@controller-0 ~]$ ovn-nbctl get logical-switch 672ca1fc-f2a8-44f0-bb5d-c98a47ae8abf external_ids
      {"neutron:availability_zone_hints"="", "neutron:mtu"="9000", "neutron:network_name"=provider1, "neutron:provnet-network-type"=flat, "neutron:revision_number"="2", "neutron_bgpvpn:type"=l3, "neutron_bgpvpn:vni"="1001"}
      

       

      Expectation:
      There must be EDPM parameters for user to specify the VPN type and VNI ID or ovn-bgp-agent must handle it with hard-coded values. Setting the external_ids after the deployment is not recommended.

       

              Unassigned Unassigned
              rh-ee-spk Spoorthi K (Inactive)
              rhos-dfg-networking-squad-bgp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: