Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-5883

Network Manager does not create the default prefix route when the ovs-bridge.datapath-type is netdev

    • NetworkManager-1.45.6-1.el9
    • None
    • None
    • sst_network_management
    • ssg_networking
    • 24
    • 5
    • False
    • Hide

      None

      Show
      None
    • No
    • Red Hat Enterprise Linux
    • None
    • Hide

      Given a system administratorconfiguring an ovs-interface attached to an ovs-bridge with datapath-type set to 'netdev',
      When they execute the provided script (See description) to set up the network,
      Then a default prefix route should be created in addition to any manually defined routes.

      Definition of Done

      • The implementation meets the acceptance criteria
      • Unit and integration tests are written and passed
      • The code is part of build attached to an errata
         
      Show
      Given a system administratorconfiguring an ovs-interface attached to an ovs-bridge with datapath-type set to 'netdev', When they execute the provided script (See description) to set up the network, Then a default prefix route should be created in addition to any manually defined routes. Definition of Done The implementation meets the acceptance criteria Unit and integration tests are written and passed The code is part of build attached to an errata  
    • None
    • None
    • None

      The default prefix route is not installed when the interface is an ovs-interface attached to an ovs-bridge of ovs-bridge.datapath-type netdev. This is also true when the configuration includes additional routes, i.e. `pv4.routes "1.1.1.0/24 40`

       

      This can simply be replicated with the following:

       

      # Wipe OVS configuration, and set it up for OVS-DPDK:
        systemctl stop openvswitch
        rm -f /etc/openvswitch/conf.db
        systemctl restart openvswitch
        ovs-vsctl set Open_vSwitch . other_config:dpdk-init=true
        systemctl restart openvswitch
        # Configure NM
        for conn in $(nmcli -g NAME c | grep br-ex); do nmcli c del "$conn"; done
        for conn in $(nmcli -g NAME c | grep ovs-); do nmcli c del "$conn"; done
        # journalctl -f -u NetworkManager | tee networkmanager.log
        nmcli general logging level trace
        nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 1500 connection.autoconnect-slaves 1 ovs-bridge.datapath-type netdev connection.autoconnect no
        nmcli c add type ovs-port conn.interface ens2f1np1 master br-ex con-name ovs-port-phys0 connection.autoconnect-slaves 1 connection.autoconnect no
        nmcli c add type ovs-port conn.interface br-ex master br-ex con-name ovs-port-br-ex connection.autoconnect no
        nmcli c add type 802-3-ethernet conn.interface ens2f1np1 master ovs-port-phys0 con-name ovs-if-phys0 connection.autoconnect-priority 100 connection.autoconnect-slaves 1 802-3-ethernet.mtu 1500 802-3-ethernet.cloned-mac-address 52:54:f8:da:c3:04 connection.autoconnect no
        nmcli c add type ovs-interface slave-type ovs-port conn.interface br-ex master  ovs-port-br-ex con-name ovs-if-br-ex 802-3-ethernet.mtu 1500 802-3-ethernet.cloned-mac-address 52:54:f8:da:c3:04 ipv4.method manual ipv4.addresses 1.1.1.1/24 connection.autoconnect no ipv6.method disabled
        nmcli c up br-ex
        nmcli c mod br-ex connection.autoconnect yes
        nmcli c mod ovs-if-phys0 connection.autoconnect yes
        nmcli c up ovs-if-br-ex
      

      The Networkmanager log is attached.

      $ rpm -qa | grep NetworkManager
      NetworkManager-libnm-1.42.2-8.el9_2.x86_64
      NetworkManager-1.42.2-8.el9_2.x86_64
      NetworkManager-wwan-1.42.2-8.el9_2.x86_64
      NetworkManager-bluetooth-1.42.2-8.el9_2.x86_64
      NetworkManager-ovs-1.42.2-8.el9_2.x86_64
      NetworkManager-adsl-1.42.2-8.el9_2.x86_64
      NetworkManager-team-1.42.2-8.el9_2.x86_64
      NetworkManager-tui-1.42.2-8.el9_2.x86_64
      NetworkManager-wifi-1.42.2-8.el9_2.x86_64
      NetworkManager-config-server-1.42.2-8.el9_2.noarch

            rh-ee-sfaye Stanislas Faye
            echaudro@redhat.com Eelco Chaudron
            Network Management Team Network Management Team
            Vladimir Benes Vladimir Benes
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: