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

Unable to unmanage device while NetworkManager is stopped

XMLWordPrintable

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

      None

      Show
      None
    • None
    • None
    • Hide

      Given a device (eth6 in the scenario from the descripton) and a configuration file specifying it should be unmanaged (managed=0), 

      When NetworkManager is restarted with the configuration file present, 

      Then, the device remains unmanaged after NM starts, consistent with the behavior when nmcli is used.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass 
      • The fix is part of a downstream build attached to an errata
      Show
      Given a device (eth6 in the scenario from the descripton) and a configuration file specifying it should be unmanaged (managed=0),  When NetworkManager is restarted with the configuration file present,  Then, the device remains unmanaged after NM starts, consistent with the behavior when nmcli is used. Definition of Done: The implementation meets the acceptance criteria Integration tests 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?

      Setting device as unmanaged in NetworkManager configuration files is not working. Using `nmcli d set eth6 managed no` works and is even restart persistent.

      What is the impact of this issue to you?

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

      NetworkManager-1.51.4-33602.copr.4b65e716c8.el10

      How reproducible is this bug?:

      always

      Steps to reproduce

      1. Do the following NM-ci scenario:

       

      * Stop NM
* Create NM config file "95-eth6-unmanaged.conf" with content
"""
[device.eth6-unmanaged]
match-device=interface-name:eth6
managed=0
"""
* Start NM

       

      Expected results

      eth6 should be unmanaged.

      Actual results

      eth6 is activated after NM start (or disconnected if no connection matches).

              rh-ee-sfaye Stanislas Faye
              fpokryvk@redhat.com Filip Pokryvka
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: