Bug 1861668

Summary: Fail to update vlan or MTU properties on a bridge used by a running VM(vnet tap device)
Product: Red Hat Enterprise Linux 8 Reporter: Michael Burman <mburman>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.3CC: dholler, ferferna, fge, jiji, jishi, network-qe, till
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.3.4-4.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 03:08:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Generate the network interfaces before applying the state with nmstate.
none
Apply the state with nmstatectl
none
verified.log none

Description Michael Burman 2020-07-29 08:39:48 UTC 
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.
Comment 8 Michael Burman 2020-07-30 08:15:49 UTC 
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)
Comment 9 Fernando F. Mancera 2020-08-07 09:23:07 UTC 
Created attachment 1710770 [details]
Generate the network interfaces before applying the state with nmstate.
Comment 10 Fernando F. Mancera 2020-08-07 09:23:47 UTC 
Created attachment 1710771 [details]
Apply the state with nmstatectl
Comment 11 Fernando F. Mancera 2020-08-07 09:25:50 UTC 
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)
Comment 12 Mingyu Shi 2020-08-10 09:48:11 UTC 
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
Comment 15 errata-xmlrpc 2020-11-04 03:08:06 UTC 
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