Bug 1751695

Summary:	Keep MTU settings of interface if possible after base interface MTU changes
Product:	Red Hat Enterprise Linux 8	Reporter:	Ales Musil <amusil>
Component:	nmstate	Assignee:	Gris Ge <fge>
Status:	CLOSED ERRATA	QA Contact:	Mingyu Shi <mshi>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	jiji, jishi, network-qe, till
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nmstate-0.2.3-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:00: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:
Bug Depends On:	1751079, 1770691, 1779162
Bug Blocks:	1107803

Description Ales Musil 2019-09-12 12:12:36 UTC

This bug was initially created as a copy of Bug #1751079

I am copying this bug because: 



Description of problem:

Considering scenario eth0 and two VLANs on top eth0.10 and eth.20 all of them with MTU 2000. When we change the MTU of eth0 and eth0.20 and apply this config the MTU of eth0.10 is reverted to default value (1500), but in the NM has still 2000 in the config. 


Version-Release number of selected component (if applicable):

NetworkManager-1.20.0-3.el8.x86_64

How reproducible:

100%

Steps to Reproduce:

Full reproducer is in attachment. 

Actual results:

76: dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 2200 
77: dummy_abc.10@dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 
79: dummy_abc.20@dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 2200 


Expected results:

76: dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 2200 
77: dummy_abc.10@dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 2000 
79: dummy_abc.20@dummy_abc: <BROADCAST,NOARP,UP,LOWER_UP> mtu 2200

Comment 5 errata-xmlrpc 2020-04-28 16:00: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, 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:1696