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

Support MAC referring for VLAN in `nmstatectl gc`

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

    • nmstate-2.2.50-1.el10
    • No
    • Important
    • ZStream
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Regression Exception
    • 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 valid Nmstate input where a VLAN’s base-iface is specified by MAC address,

      When the system administrator runs nmstatectl gc to generate NetworkManager keyfiles for the configuration,

      Then the output must include keyfiles where:

      • The base interface is correctly mapped from its MAC address to a usable connection name
      • The VLAN profile refers to that name so that when both profiles are placed in /etc/NetworkManager/system-connections/ and reloaded with nmcli connection reload, the VLAN can be brought up successfully with nmcli connection up <vlan> and does not fail with a “missing parent interface” error.

      Integration test case is available upstream.

      Code is reviewed and merged upstream.

      Preliminary testing is done.

      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 valid Nmstate input where a VLAN’s base-iface is specified by MAC address, When the system administrator runs nmstatectl gc to generate NetworkManager keyfiles for the configuration, Then the output must include keyfiles where: The base interface is correctly mapped from its MAC address to a usable connection name The VLAN profile refers to that name so that when both profiles are placed in /etc/NetworkManager/system-connections/ and reloaded with nmcli connection reload, the VLAN can be brought up successfully with nmcli connection up <vlan> and does not fail with a “missing parent interface” error. Integration test case is available upstream. Code is reviewed and merged upstream. Preliminary testing is done.
    • Pass
    • Automated
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • None

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

      Using NetworkManager keyfiles generated by `nmstatectl gc` for referring VLAN base interface via MAC address does not works.

      What is the impact of this issue to you?

      OpenShift need this feature

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

      nmstate-2.2.45-1.el9_6

      How reproducible is this bug?:

      100%

      Steps to reproduce

      echo '---
interfaces:
  - name: port1
    type: ethernet
    identifier: mac-address
    mac-address: 00:23:45:67:89:1a
  - name: vlan101
    type: vlan
    state: up
    vlan:
      base-iface: port1
      id: 101' | nmstatectl gc -

# Then store the output into files to /etc/NetworkManager/system-connections/ as <name>.nmconnection own by root with 0600 permission.

nmcli c reload
nmcli c up port
nmcli c up vlan101

      Expected results

      VLAN been created as desired.

      Actual results

      NM failure on not able to file parent interface of vlan.

              rh-ee-mshi1 Mingyu Shi
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: