yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1763608@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1

---------------
netplan.io (0.97-0ubuntu1~18.10.1) cosmic; urgency=medium

  * Backport netplan.io 0.97 to 18.10. (LP: #1828299)
  * Keep debian/patches/glib_changes.patch: Make sure tests work on older GLib.

netplan.io (0.97-0ubuntu1) eoan; urgency=medium

  * New upstream release: 0.97
    - networkd: force bringing up devices with no IP addresses (LP: #1763608)
    - Reworked renderer choosing to avoid regression in default renderer when
      multiple files specify it globally (LP: #1825206)
    - Fixed networkd activation. (LP: #1821867)
  * Drop all patches; they are included in the upstream release.

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Thu, 09 May 2019
11:29:56 -0400

** Changed in: netplan.io (Ubuntu Cosmic)
       Status: Fix Committed => Fix Released

** Changed in: netplan.io (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763608

Title:
  Netplan ignores Interfaces without IP Addresses

Status in netplan:
  Fix Committed
Status in neutron:
  Invalid
Status in netplan.io package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released
Status in netplan.io source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Netplan users who need to bring up an interface (set its flag to IFF_UP) but not define an address, using the networkd renderer, as the interface may be further managed via another tool.

  [Test case]
  1) Install Ubuntu
  2) Set up netplan; with the following different use cases:

  == New VLAN ==

  network:
    version: 2
    renderer: networkd
    ethernets:
      [... whatever is already configured for the system...]
    vlans:
      vlan100:
        link: <the existing ethernet>
        id: 100

  == Bring up an existing secondary interface ==

  network:
    version: 2
    renderer: networkd
    ethernets:
      eth0: {}

  
  3) Verify that in both cases, the interface (ethernet or VLAN) is brought up and shows UP, LOWER_UP flags in the output of 'ip link'.

  
  [Regression potential]
  As this brings a behavior change in netplan where as soon as an interface is listed in the netplan YAML, it will be brought up, care should be taken with existing configurations that do work, if specific devices are listed but are not assigned an IP address, as they will be brought up by networkd. This is expected to be a limited number of cases already, and impact to network installations is minimal.

  
  ----

  The "manual" method in /etc/network/interfaces resulted in an
  interface being brought up, but not having an IP address assigned.

  When configuring an Interface without an IP Address, netplan ignores
  the interface instead of bringing it up.

  ---
  network:
    version: 2
    renderer: networkd
    ethernets:
      eth1: {}

  Expected result from `netplan apply`: eth1 is brought up.
  Actual result: eth1 is still down.

  Similarly `netplan generate` does not generate any file in
  /run/systemd/network for eth1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1763608/+subscriptions