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

`connection.autoconnect-ports` of OVS port is not working

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • NetworkManager-1.55.4-1.el10
    • Yes
    • Low
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      The acceptance criteria defined below are met.

      Given an OVS bridge with a bond port and dummy interfaces
      When the bridge is activated via nmstate
      Then, NetworkManager should also activate the port and interfaces if connection.autoconnect-ports = yes and ovs-vsctl show should reflect the full topology.

      Integration test case is available upstream

      Code is reviewed and merged

      Preliminary testing is done

      A demo is recorded

       

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: The acceptance criteria defined below are met. Given an OVS bridge with a bond port and dummy interfaces When the bridge is activated via nmstate Then, NetworkManager should also activate the port and interfaces if connection.autoconnect-ports = yes and ovs-vsctl show should reflect the full topology. Integration test case is available upstream Code is reviewed and merged Preliminary testing is done A demo is recorded  
    • Pass
    • Automated
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Nmstate failed to create a ovs bond.

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      NetworkManager-1.53.4-1.el10.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce

      sudo dnf install nmstate-2.2.44-1.el10 -y
echo '
interfaces:
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: ovs-bond0
      link-aggregation:
        mode: balance-slb
        port:
        - name: dummy1
        - name: dummy2
- name: dummy1
  type: dummy
  state: up
- name: dummy2
  type: dummy
  state: up
' | sudo nmstatectl apply - --no-verify

sudo ovs-vsctl show

      Expected results

          Bridge br0
        Port ovs-bond0
            Interface dummy1
                type: system
            Interface dummy2
                type: system

      Actual results

      No OVS bridge been created.

      Extra info

      Nmstate only request the activation on OVS bridge, and hoping `connection.autoconnect-ports` bring up the OVS port and OVS interfaces.

      This works well on NetworkManager-1.52.0-3.el10_0 , hence set regression flag.

      Nmstate will create workaround on this issue. So low priority.

        1. nm.log
          79 kB

              rhn-engineering-vbenes Vladimir Benes
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: