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

Cannot change bond port setting for MAC matching connection

XMLWordPrintable

    • No
    • Moderate
    • rhel-sst-network-management
    • ssg_networking
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Given a bond port configuration in NetworkManager that uses MAC address matching and a supported bonding mode for priority settings,

      When the configuration is applied,

      Then the specified bond-port.prio should be set correctly to the desired value or an error message should indicate if the configuration mode does not support this setting.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass
      • The code is part of a downstream build attached to an errata
      Show
      Given a bond port configuration in NetworkManager that uses MAC address matching and a supported bonding mode for priority settings, When the configuration is applied, Then the specified bond-port.prio should be set correctly to the desired value or an error message should indicate if the configuration mode does not support this setting. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The code is part of a downstream build attached to an errata
    • None
    • None
    • None

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

      When a bond port is using `802-3-ethernet.mac-address=$MAC` for matching instead of `connection.interface-name`, activating NM connection cannot apply config of `bond-port.prio`

      What is the impact of this issue to you?

      Nmstate is introducing new way to match bond port via MAC address, this will stop people from applying bond port settings.

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

      NetworkManager-1.51.3-33586.copr.4082e7e109.el9.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce

      Run attached bug.sh

      Expected results

      No failure, bond port priority set to 10

      Actual results

      The bond port prio is still 0

        1. nm.log
          961 kB
        2. bug.sh
          0.9 kB

              rh-ee-sfaye Stanislas Faye
              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:
                Resolved: