[Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
Mathieu Trudel-Lapierre
mathieu.tl at gmail.com
Mon Mar 11 20:45:21 UTC 2019
** Description changed:
+ [Impact]
+ Users of netplan with complex bridge or bond configurations, where setting MTU or renaming is required and matching is done by MAC address.
+
+ [Test case]
+ 1) Configure netplan with a bond, and device members that use different MTU values:
+
+ network:
+ version: 2
+ ethernets:
+ ens6:
+ set-name: ens6
+ match:
+ macaddress: 52:54:00:25:ba:4f
+ mtu: 9000
+ ens7:
+ set-name: ens7
+ match:
+ macaddress: 52:54:00:02:86:3b
+ mtu: 9000
+ bonds:
+ bond0:
+ interfaces:
+ - ens6
+ - ens7
+ mtu: 9000
+ parameters:
+ down-delay: 0
+ lacp-rate: fast
+ mii-monitor-interval: 100
+ mode: 802.3ad
+ up-delay: 0
+ transmit-hash-policy: layer3+4
+ vlans:
+ bond0.804:
+ mtu: 1500
+ id: 804
+ link: bond0
+ addresses:
+ - 10.20.16.50/24
+ bond0.1:
+ mtu: 1500
+ id: 1
+ link: bond0
+ addresses:
+ - 10.3.67.31/20
+ gateway4: 10.3.67.1
+ nameservers:
+ addresses:
+ - 10.3.67.22
+ search:
+ - cloud
+
+ 2) Verify that the correct MTU has been applied to each interface:
+ ens6: 9000
+ ens7: 9000
+ bond0: 9000
+ bond0.804: 1500
+ bond0.1: 1500
+
+
+ [Regression potential]
+ Minimal risk of regression: this changes the generated configuation in a very targetted way, where only when dealing with an interface added to bond or a bridge *and* matching by MAC address is in use, the generated configuration for networkd is further qualified by device Type to ensure it does not match on extra devices (ie. because some may share the same MAC address). Other configurations (such has when no matching is in use) are not affected.
+
+
+ ---
+
+
netplan version: 0.36.3
Ubuntu Bionic
"""
network:
- version: 2
- vlans:
- bond0.810:
- addresses:
- - 10.20.33.3/29
- id: 810
- link: bond0
- mtu: 1500
- nameservers: *id001
+ version: 2
+ vlans:
+ bond0.810:
+ addresses:
+ - 10.20.33.3/29
+ id: 810
+ link: bond0
+ mtu: 1500
+ nameservers: *id001
"""
Note: bond0 and its slaves have mtu=9000 configured (there are other
vlans using 9000, too).
On netplan source code deployed by the package, only "migrate.py" has
references to "MTU", however, a command does not exist for "migrate".
I also tried to add /etc/udev/rules.d/70-net.rules:
"""
SUBSYSTEM=="net", ACTION=="add", KERNEL=="bond0.810", ATTR{mtu}=="9000", ATTR{mtu}="1500"
"""
But it doesn't get applied.
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1804861
Title:
MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
Status in netplan:
Fix Released
Status in maas package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Bug description:
[Impact]
Users of netplan with complex bridge or bond configurations, where setting MTU or renaming is required and matching is done by MAC address.
[Test case]
1) Configure netplan with a bond, and device members that use different MTU values:
network:
version: 2
ethernets:
ens6:
set-name: ens6
match:
macaddress: 52:54:00:25:ba:4f
mtu: 9000
ens7:
set-name: ens7
match:
macaddress: 52:54:00:02:86:3b
mtu: 9000
bonds:
bond0:
interfaces:
- ens6
- ens7
mtu: 9000
parameters:
down-delay: 0
lacp-rate: fast
mii-monitor-interval: 100
mode: 802.3ad
up-delay: 0
transmit-hash-policy: layer3+4
vlans:
bond0.804:
mtu: 1500
id: 804
link: bond0
addresses:
- 10.20.16.50/24
bond0.1:
mtu: 1500
id: 1
link: bond0
addresses:
- 10.3.67.31/20
gateway4: 10.3.67.1
nameservers:
addresses:
- 10.3.67.22
search:
- cloud
2) Verify that the correct MTU has been applied to each interface:
ens6: 9000
ens7: 9000
bond0: 9000
bond0.804: 1500
bond0.1: 1500
[Regression potential]
Minimal risk of regression: this changes the generated configuation in a very targetted way, where only when dealing with an interface added to bond or a bridge *and* matching by MAC address is in use, the generated configuration for networkd is further qualified by device Type to ensure it does not match on extra devices (ie. because some may share the same MAC address). Other configurations (such has when no matching is in use) are not affected.
---
netplan version: 0.36.3
Ubuntu Bionic
"""
network:
version: 2
vlans:
bond0.810:
addresses:
- 10.20.33.3/29
id: 810
link: bond0
mtu: 1500
nameservers: *id001
"""
Note: bond0 and its slaves have mtu=9000 configured (there are other
vlans using 9000, too).
On netplan source code deployed by the package, only "migrate.py" has
references to "MTU", however, a command does not exist for "migrate".
I also tried to add /etc/udev/rules.d/70-net.rules:
"""
SUBSYSTEM=="net", ACTION=="add", KERNEL=="bond0.810", ATTR{mtu}=="9000", ATTR{mtu}="1500"
"""
But it doesn't get applied.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1804861/+subscriptions
More information about the foundations-bugs
mailing list