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

ovs bonding with managed and unmanaged interface fails

XMLWordPrintable

    • Yes
    • Important
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 4
    • 3
    • False
    • Hide

      None

      Show
      None
    • No
    • NMT - RHEL-9.5 DTM 2
    • Hide

      Given a system administrator has configured an ovs-bridge with a mix of managed (e.g., eth1) and unmanaged (e.g., cali* interfaces from Calico CNI) interfaces,

      When the administrator applies the configuration using NMstate to create an ovs-bridge bonding with secondary and primary interfaces, where the primary interface is an unmanaged interface generated by Calico CNI,

      Then NMstate should successfully create the ovs-bridge as specified, without errors related to the management state of any interface.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Unit test and integration test are written and pass
      • The fix is part of a downstream build attached to an errata 
      Show
      Given a system administrator has configured an ovs-bridge with a mix of managed (e.g., eth1) and unmanaged (e.g., cali* interfaces from Calico CNI) interfaces, When the administrator applies the configuration using NMstate to create an ovs-bridge bonding with secondary and primary interfaces, where the primary interface is an unmanaged interface generated by Calico CNI, Then NMstate should successfully create the ovs-bridge as specified, without errors related to the management state of any interface. Definition of Done: The implementation meets the acceptance criteria Unit test and integration test are written and pass The fix is part of a downstream build attached to an errata 
    • None
    • None
    • None

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

      At kubernetes-nmstate we have a test that do a ovs-bridge bonding with secondary and primary interfaces, the primary interface is an interface generated by calico CNI so it's un managed

       

      This was working fine at nmstate-2.2.23-1.el9 but using nmstate git copr 
      2.2.24-0.alpha.20240125.42936b17.el9
      is failing now.

       

      Please provide the package NVR for which bug is seen:

      2.2.24-0.alpha.20240125.42936b17.el9

      How reproducible: Always

      Steps to reproduce

      1. Create an unmanaged interface (in that case calico one)
      2. Do a ovs-bridge bonding with it
      
interfaces:
      - bridge:
          options:
            stp: false
          port:
          - link-aggregation:
              mode: balance-slb
              port:
              - name: cali759043bfdc4
              - name: eth1
            name: bond38
        name: br38
        state: up
        type: ovs-bridge

      Expected results

      ovs-bridge is created as expected

      Actual results

      [2024-01-26T19:16:27Z INFO nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(DependencyFailed): Activation failed because the device is unmanaged
       

      NetworkManager version
      NetworkManager x86_64 1:1.45.10-1.el9 baseos 2.3 M

              fge@redhat.com Gris Ge
              ellorent Felix Enrique Llorente Pastora
              Gris Ge Gris Ge
              Mingyu Shi Mingyu Shi
              Mayur Patil Mayur Patil
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: