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.
Description of problem:
This is to address the issue described in https://bugzilla.redhat.com/show_bug.cgi?id=1929317#c4.
When a host is configured as following:
[eth0]--[bond1]--[vlan10]--[OVS bridge]
[eth1]-/
And the desired state is adding a VLAN iface and a linux bridge, so the resulting config would look like:
[eth0]--[bond1]--[vlan10]--[OVS bridge]
[eth1]-/ \---[vlan20]--[linux bridge]
nmstate fails the configuration.
Version-Release number of selected component (if applicable):
nmstate 0.3
How reproducible:
Always
Steps to Reproduce:
1. Get a host with a topology similar to the one described above.
2. Apply:
interfaces:
- name: bond1.1044
type: vlan
state: up
vlan:
base-iface: bond1
id: 1044
- name: br-ext2
description: br-ext2 with bond1.1044
type: linux-bridge
state: up
ipv4:
enabled: false
bridge:
options:
stp:
enabled: false
port:
- name: bond0.1044
Actual results:
This fails with a complaint about the OVS bridge.
Expected results:
The new VLAN and bridge should be configured without touching the existing topology.
Additional info:
This does not fail on 8.4.
Find more details about reproducers in the original BZ https://bugzilla.redhat.com/show_bug.cgi?id=1929317
Hello @fge, we failed to reproduce this issue outside customer's environment. Your team provided a fix a while back and it seems that it resolved this issue https://bugzilla.redhat.com/show_bug.cgi?id=1929317#c24. Therefore, I think we can close this BZ unless you want to cover this by QE. Whichever you prefer.
Comment 2Fernando F. Mancera
2021-06-08 09:12:19 UTC
Our QA verified the OVS issue that was causing this. Therefore I am closing this as CURRENTRELEASE. Thanks Petr.