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

Add API to manage permanent unmanaged rules

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

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • NetworkManager
    • None
    • None
    • rhel-net-mgmt
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • 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 a system running NetworkManager with the new unmanaged-rule API enabled,

      When a client adds, lists, and removes unmanaged rules by interface name, MAC address, and PCI address via the API,

      Then NetworkManager persists the rules in NM.intern.conf, reports them accurately through the “list” call, and stops or resumes managing the matching devices immediately after each API call.

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) 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 a system running NetworkManager with the new unmanaged-rule API enabled, When a client adds, lists, and removes unmanaged rules by interface name, MAC address, and PCI address via the API, Then NetworkManager persists the rules in NM.intern.conf, reports them accurately through the “list” call, and stops or resumes managing the matching devices immediately after each API call. ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Nmstate needs a supported way to tell NetworkManager to unmanaged a device when state: absent is applied, and later resume management when state: up is requested.
      Today we can only do that with temporary runtime flags.
      The goal of this feature request is to add a public API that lets clients add, list, and remove permanent unmanaged rules keyed by interface name, MAC address, or PCI address, with NetworkManager storing those rules in NM.intern.conf so they survive restarts.
      This lets nmstate block autoconnect profiles while an interface is absent and safely restore normal management afterward.

              nm-team Network Management Team
              rh-ee-sfaye Stanislas Faye
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: