Comment 11 for bug 1804861
Revision history for this message
| Ryan Harper (raharper) wrote Re: [Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Thanks for the information. I can confirm what Mathieu is seeing in
Case C. Initially when I deploy your netplan config, all of the MTU
settings are correct
due to the .link files already being triggered; it's somewhat of a
race with udev and when the underlying interfaces come up.
The juju scenario though almost ensures that we'll hit a case where
the vlan has the correct MTU initially, juju eventually calls netplan
apply
which can trigger the system to apply .link files which for the bonds,
will match additional interfaces due to use of the underlying MAC
address.
As suggested, one possible workaround is for MAAS to generate MAC
values for bridges/bonds and ensure they're not one of the physical
device
MAC values; this would ensure .link rules which use MAC matching won't
apply. I don't know the ramifications of that w.r.t deployments of
switches
and other things which sometimes want/need to know what MAC will show
up on which port etc.
On the netplan side, if a bond or bridge is assigned a MAC from one of
the ethernet devices, it could emit additional properties in the
ethernet
.link file to prevent the .link from applying to devices other than
the actual bond members.
In the two bond member's .link files:
# cat 10-netplan-
[Match]
MACAddress=
Type=!vlan bridge bond
[Link]
WakeOnLan=off
MTUBytes=9000
On Wed, Nov 28, 2018 at 7:50 AM Francis Ginther
<email address hidden> wrote:
>
> ** Tags added: id-5bfdb43fc074
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> MTU size defined on /etc/netplan/
>
> To manage notifications about this bug go to:
> https:/