yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
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/1774666

Title:
  Bond interfaces stuck at 1500 MTU on Bionic

Status in cloud-init:
  Fix Released
Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in cloud-init source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in cloud-init source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Invalid
Status in cloud-init source package in Cosmic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Confirmed

Bug description:
  When deploying a machine through MAAS with bonded network interfaces,
  the bond does not have a 9000 byte MTU applied despite the attached
  VLANs having had a 9000 MTU explicitly set. The MTU size is set on the
  bond members, but not on the bond itself in Netplan. Consequently,
  when the bond is brought up, the interface MTU is decreased from 9000
  to 1500. Manually changing the interface MTU after boot is successful.

  This is not observed when deploying Xenial on the same machine. The
  bond comes up at the expected 9000 byte MTU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1774666/+subscriptions