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

Reapply on bridge port did not reset default-pvid

XMLWordPrintable

    • NetworkManager-1.48.10-1.el9
    • None
    • Low
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 3
    • False
    • Hide

      None

      Show
      None
    • No
    • NMT - RHEL-9.5 DTM 24
    • Hide

      Given a system administrator has configured a network bridge br0 with a default-pvid and an attached port dummy1 under NetworkManager,

      When they change the default-pvid of br0 and reapplies the configuration to both br0 and dummy1 using nmcli commands,

      Then NetworkManager should update the VLAN configuration for dummy1 by removing the previous default-pvid and applying the new default-pvid.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration test are written and pass
      • The code is part of a downstream build attached to an errata
      Show
      Given a system administrator has configured a network bridge br0 with a default-pvid and an attached port dummy1 under NetworkManager, When they change the default-pvid of br0 and reapplies the configuration to both br0 and dummy1 using nmcli commands, Then NetworkManager should update the VLAN configuration for dummy1 by removing the previous default-pvid and applying the new default-pvid. Definition of Done : The implementation meets the acceptance criteria Integration test are written and pass The code is part of a downstream build attached to an errata
    • Pass
    • None
    • Release Note Not Required
    • None

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

      The `nmcli device reapply` did not reset port's VLAN filtering base on linux bridge's default-pvid setting, causing leftover VLANs.

      For below example, the `br0` has changed default-pvid from 900 to 901, the reapply on `br0` and `dummy1` should refresh vlan settings on `dummy1`, but
      noticed the VLAN `900` still exits as leftover.

      Please provide the package NVR for which bug is seen:

      NetworkManager-1.47.1-33100.copr.9920a4b576.el9.x86_64

      How reproducible:

      100%

      Steps to reproduce

      echo '
---
interfaces:
- name: dummy1
  type: dummy
- name: br0
  type: linux-bridge
  state: up
  bridge:
    options:
      vlan-default-pvid: 900
      stp:
        enabled: false
    port:
    - name: dummy1
      vlan:
        enable-native: true
        mode: trunk
        tag: 300
        trunk-tags:
        - id: 101
        - id: 102
' | nmstatectl set -

bridge vlan

nmcli c modify br0 bridge.vlan-default-pvid 901
nmcli d reapply br0
nmcli d reapply dummy1

bridge vlan

      Expected results

      port              vlan-id
br0               901 PVID Egress Untagged
dummy1            101
                  102
                  300 PVID Egress Untagged
                  901 Egress Untagged

      Actual results

      port              vlan-id
br0               901 PVID Egress Untagged
dummy1            101
                  102
                  300 Egress Untagged
                  900 Egress Untagged
                  901 PVID Egress Untagged

      Business impact:

      This bug is found during effort on integrating nmstate into OpenShift day1 configuration. Nmstate can workaround this by doing full reactivation on impacted bridge ports, the bug report is just for reference.

      You may close it as won't fix.

              ihuguet@redhat.com Inigo Huguet
              fge@redhat.com Gris Ge
              Inigo Huguet Inigo Huguet
              David Jaša David Jaša
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: