yahoo-eng-team team mailing list archive

[Chad Smith <1836949@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 19.2-2. 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/1836949

Title:
  mtu gets lost in translation from netplan (v2) yaml

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  MTU values get lost in translation when input is netplan (v2 yaml).

  I'm attaching a recreate script, but basically the mtu setting gets
  lost when writing ENI or sysconfig if the input is v2 yaml.

  input of:
    version: 2
    vlans:
      bond0.1000:
        addresses: ["192.6.1.9/24"]
        id: 1000
        link: bond0
        mtu: 1496
      bond0.1001:
        id: 1001
        link: bond0
    bonds:
      bond0:
        interfaces: ["enp0s0", "enp0s1"]
        parameters: {}
        mtu: 1496

  Renders output files like etc/sysconfig/network-scripts/ifcfg-bond0:
    # Created by cloud-init on instance boot automatically, do not edit.
    #
    BONDING_MASTER=yes
    BONDING_SLAVE0=enp0s0
    BONDING_SLAVE1=enp0s1
    BOOTPROTO=none
    DEVICE=bond0
    NM_CONTROLLED=no
    ONBOOT=yes
    STARTMODE=auto
    TYPE=Bond
    USERCTL=no

  Where the same config from v1 would have the 'MTU=1496'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cloud-init 19.1-1-gbaa47854-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CloudName: LXD
  Date: Wed Jul 17 18:37:04 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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