Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionQuique Llorente
2022-03-23 07:06:19 UTC
Description of problem:
To reset vlan-filtering from a linux bridge it was possible to specify "vlan: {}" at the bridge port, this is no longer the case and it get merged with previous vlan config so it isn't reset.
Version-Release number of selected component (if applicable):
nmstate-1.0.2-18.el8.noarch
How reproducible:
Always
Steps to Reproduce:
1. Create a linux-bridge with vlan-filtering
nmstatectl apply << EOF
> interfaces:
> - name: dummy1
> type: dummy
> state: up
> - name: linux-br0
> type: linux-bridge
> state: up
> bridge:
> port:
> - name: dummy1
> stp-hairpin-mode: false
> stp-path-cost: 100
> stp-priority: 32
> vlan:
> mode: trunk
> trunk-tags:
> - id: 101
> - id-range:
> min: 500
> max: 599
> tag: 100
> enable-native: true
> EOF
2. Reset the vlan-filtering at the bridge
nmstatectl apply << EOF
> interfaces:
> - name: dummy1
> type: dummy
> state: up
> - name: linux-br0
> type: linux-bridge
> state: up
> bridge:
> port:
> - name: dummy1
> stp-hairpin-mode: false
> stp-path-cost: 100
> stp-priority: 32
> vlan: {}
> EOF
Actual results:
Vlan configuration is still there
The vlan configuration is still there
nmstatectl show linux-br0 |grep vlan -A 8
vlan:
enable-native: true
mode: trunk
tag: 100
trunk-tags:
- id: 101
- id-range:
max: 599
min: 500
Expected results:
The vlan configuration should be gone
Additional info:
It was discover as part of https://github.com/nmstate/nmstate/pull/1830, it also found that there is a false possitive at the test_disable_vlan_filtering_on_bridge integration test
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7465
Description of problem: To reset vlan-filtering from a linux bridge it was possible to specify "vlan: {}" at the bridge port, this is no longer the case and it get merged with previous vlan config so it isn't reset. Version-Release number of selected component (if applicable): nmstate-1.0.2-18.el8.noarch How reproducible: Always Steps to Reproduce: 1. Create a linux-bridge with vlan-filtering nmstatectl apply << EOF > interfaces: > - name: dummy1 > type: dummy > state: up > - name: linux-br0 > type: linux-bridge > state: up > bridge: > port: > - name: dummy1 > stp-hairpin-mode: false > stp-path-cost: 100 > stp-priority: 32 > vlan: > mode: trunk > trunk-tags: > - id: 101 > - id-range: > min: 500 > max: 599 > tag: 100 > enable-native: true > EOF 2. Reset the vlan-filtering at the bridge nmstatectl apply << EOF > interfaces: > - name: dummy1 > type: dummy > state: up > - name: linux-br0 > type: linux-bridge > state: up > bridge: > port: > - name: dummy1 > stp-hairpin-mode: false > stp-path-cost: 100 > stp-priority: 32 > vlan: {} > EOF Actual results: Vlan configuration is still there The vlan configuration is still there nmstatectl show linux-br0 |grep vlan -A 8 vlan: enable-native: true mode: trunk tag: 100 trunk-tags: - id: 101 - id-range: max: 599 min: 500 Expected results: The vlan configuration should be gone Additional info: It was discover as part of https://github.com/nmstate/nmstate/pull/1830, it also found that there is a false possitive at the test_disable_vlan_filtering_on_bridge integration test