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:
Fail to update vlan or MTU properties on a bridge used by a running VM(vnet tap device).

RHV support flows to allow the user/admin to be able to update a vlan or custom MTU properties on a bridge while it is used by a running VM(vnet).

This flows are working find on 0.2.10, but broken on 0.3.4-3
This should be fixed to aloow this flows in RHV.

Version-Release number of selected component (if applicable):
nmstate-0.3.4-3.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Have a bridge attached to a host and used by a running VM(vnet)
2. Try to update bridge's vlan or MTU property

Actual results:
Fail on nmstate validation. This validation wasn't in 0.2

Expected results:
Should be allowed

Additional info:
This is failing automation tests in RHV QE suite.

Issue fixed with 0.3.4-4, tested RHV flow with success on nmstate-0.3.4-6.el8.noarch. tnx for a quick fix)

Created attachment 1710770 [details]
Generate the network interfaces before applying the state with nmstate.

Created attachment 1710771 [details]
Apply the state with nmstatectl

In order to reproduce this issue:

1. Execute reproducer.sh attached.
2. Then apply the reproduce_state.yml using nmstatectl.
3. Run `nmstatectl show bridge0`, it should contains both ports (tap0 and eth1)

Created attachment 1710939 [details]
verified.log

Verified with versions:
nmstate-0.3.4-10.el8.noarch
NetworkManager-1.26.0-2.el8.x86_64
DISTRO=RHEL-8.3.0-20200728.n.0
Linux dell-r330-15.gsslab.brq.redhat.com 4.18.0-228.el8.x86_64 #1 SMP Mon Jul 27 06:05:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
openvswitch-selinux-extra-policy-1.0-19.el8fdp.noarch
openvswitch2.13-2.13.0-49.el8fdp.x86_64
python3-openvswitch2.13-2.13.0-49.el8fdp.x86_64

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-2020:4696