Public bug reported: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1)
This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) ** Affects: cloud-init Importance: Undecided Status: New ** Affects: maas Importance: Undecided Status: New ** Attachment added: "network v1/v2 configs from maas/curtin and corresponding /etc/network/interfaces.d/50-cloud-init.cfg" https://bugs.launchpad.net/bugs/1835008/+attachment/5274586/+files/cloud-init.tar -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1835008 Title: network_v2 does not set mtu on eni config Status in cloud-init: New Status in MAAS: New Bug description: The MTU is not set on the bond, nor vlans on the bond, nor the bridges attached to the vlans on a network_v2 configuration. It's only set on the underlying interfaces (eth0, eth1) This does not happen if given a network_v1 configuration. (I'm deploying ubuntu xenial via MAAS 2.6.0, setting force_v1_network_yaml=true is my current workaround.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1835008/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp