yahoo-eng-team team mailing list archive

[Chad Smith <1724895@xxxxxxxxxxxxxxxxxx>]

Marking this invalid for cloud-init per netplan symptoms 'fixed' in
https://bugs.launchpad.net/netplan/+bug/1807273 look like it might be
the same case here with no change to cloud-init

** Changed in: cloud-init
       Status: New => Invalid

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

Title:
  MTU not applied on private ethernet interfaces

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Won't Fix

Bug description:
  == cloud-init query ==

  Cloud-init isn't adding MAC addresses in the match stanza for various
  network interfaces in /etc/netplan/50-cloud-init.yaml, which is
  leading to unexpected results. Is there any reason this would happen?

  
  == Original Description ==

  Running nplan 0.30 on Ubuntu 17.10. From what I can tell, the
  ethernets/interface/mtu field isn't applied when testing against a
  private ethernet adapter.

  Using a netplan yaml file (/etc/netplan/10-ens7.yaml):

  ---

  network:
    version: 2
    renderer: networkd
    ethernets:
      ens7:
        mtu: 1450
        dhcp4: no
        addresses: [10.99.0.13/16]

  ---

  Then running "netplan apply" (or rebooting), yields the following:

  ---

  6: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether 52:54:00:2a:19:bc brd ff:ff:ff:ff:ff:ff
      inet 10.99.0.13/16 brd 10.99.255.255 scope global ens7
         valid_lft forever preferred_lft forever
      inet6 fe80::5054:ff:fe2a:19bc/64 scope link
         valid_lft forever preferred_lft forever

  ---

  Is this a bug in netplan, or am I misunderstanding the YAML syntax?

  Best,
  Andrew

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