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

Drop support for the `slaves-order` option in NetworkManager.conf

    • NetworkManager-1.45.9-1.el9
    • None
    • None
    • 1
    • rhel-sst-network-management
    • 22
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL 8.10/9.4 DTM 14
    • Hide

      Given a system administrator managing network configurations using NetworkManager,
      When they access and modify the NetworkManager.conf file in RHEL8 or later versions,
      Then they should not see or be able to use the slaves-order option, as its support should be completely removed

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Unit test and integration test are written and pass
      • The code is part of a build attached to an errata
      Show
      Given a system administrator managing network configurations using NetworkManager, When they access and modify the NetworkManager.conf file in RHEL8 or later versions, Then they should not see or be able to use the slaves-order option, as its support should be completely removed Definition of Done: The implementation meets the acceptance criteria Unit test and integration test are written and pass The code is part of a build attached to an errata
    • Pass
    • Automated
    • None

      NetworkManager supports a `slaves-order` option in NetworkManager.conf to control the order of activation of ports at boot.

      slaves-order
      This key specifies in which order slave connections are auto-activated on boot or when the master activates them. Allowed values are name (order connection by interface name, the default), or index (order slaves by their kernel index).

      This property was introduced only to allow keeping the old behavior in RHEL7, while the default order was changed from `ifindex` to `name` in RHEL8. The usefulness of this option is questionable, as `name` together with predictable interface names should give a predictable order. When not using predictable interface names, the name is unpredictable but so is the ifindex. And in any case, interfaces can appear at any time and so the concept of "order" is not very useful.

              ferferna Fernando Fernandez Mancera
              bgalvani@redhat.com Beniamino Galvani
              Network Management Team Network Management Team
              Matej Berezny Matej Berezny (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: