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

Nmstate creating keyfiles when not required (altnames)

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • rhel-8.6.0
    • nmstate
    • None
    • No
    • None
    • rhel-net-mgmt
    • 2
    • 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 an ethernet interface eno1np0 with MAC 0c:42:a1:56:01:fe exists with no existing NetworkManager profile and /etc/NetworkManager/system-connections/ is empty,

      When a sysadmin applies nmstate YAML that sets only an ethernet interface eno1np0 by MAC with alt-name primarycni,

      Then command 'ip link show eno1np0' output includes 'altname primarycni' and directory /etc/NetworkManager/system-connections/ remains empty and 'nmcli connection show' does not list eno1np0.

      ( ) 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 an ethernet interface eno1np0 with MAC 0c:42:a1:56:01:fe exists with no existing NetworkManager profile and /etc/NetworkManager/system-connections/ is empty, When a sysadmin applies nmstate YAML that sets only an ethernet interface eno1np0 by MAC with alt-name primarycni, Then command 'ip link show eno1np0' output includes 'altname primarycni' and directory /etc/NetworkManager/system-connections/ remains empty and 'nmcli connection show' does not list eno1np0. ( ) 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

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

      Solely adding altnames to an interface should not create NetworkManager keyfiles in /etc/NetworkManager/system-connections.

       

         interfaces:
      - name: eno1np0
        type: ethernet
        identifier: mac-address
        mac-address: 0c:42:a1:56:01:fe
        alt-names:
          - name: primarycni

       

      What is the impact of this issue to you?

      On an OpenShift OVN-Kubernetes cluster, the configure-ovs.sh script will move the keyfiles to /run/NetworkManager/system-connections. Applying altnames to the br-ex enslaved interface (eno1np0 in the example above) will create a keyfile in /etc and interfere with the running configuration and the network configuration upon node reboot.

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

      nmstate-2.2.54-1.el9_6.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      No keyfiles created when the only desired configuration is adding/removing altnames.

      Actual results

              nm-team Network Management Team
              carlosgoncalves Carlos Goncalves
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: