[Bug 1756742] Re: Fresh bionic installs with DI don't mention netplan in ENI

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.10.4

---------------
nplan (0.32~17.10.4) artful; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
    "mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
    denote the migration to using netplan. (LP: #1756742)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
    with Windows Server-based DHCP servers which don't support RFC 4361.
    (LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
    can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
    and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
    connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
    YAML configurations in that directory, we just need to remove generated
    wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Tue, 08 May 2018
11:04:30 -0400

** Changed in: nplan (Ubuntu Artful)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to finish-install in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1756742

Title:
  Fresh bionic installs with DI don't mention netplan in ENI

Status in netplan:
  Fix Committed
Status in finish-install package in Ubuntu:
  Triaged
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  All users of netplan on new installs of Ubuntu 18.04.

  [Test case]
  1) Install 18.04.
  2) Open /etc/network/interfaces for editing.
  3) Verify that it contains text to notify the user that Ubuntu 18.04 now uses netplan for network configuration.

  [Regression Potential]
  Upgraded systems and other customized installations may already contain /etc/network/interfaces with existing settings for network devices. These should not have the /etc/network/interfaces file modified in any way, and retain previous network settings and connectivity. Behavior changes in systems running ifupdown instead of netplan may indicate a potential regression caused by netplan modifying /etc/network/interfaces. Newly installed systems should include the appropriate netplan configuration for that system under /etc/netplan/*.yaml (either as configuration from the installer, in which case static IPs or DHCP may be used, or as a simple file setting the renderer to "NetworkManager" in the case of desktop installs). Newly installed systems should additionally include a comments-only /etc/network/interfaces pointing to /etc/netplan. Changes in connectivity behavior on existing installs should be investigated as possible regressions. Changes in connectivity behavior in new installs (compared to previous releases) would typically not be regressions from this SRU, but should be noted as possible limitations in netplan, and thus require bug reports.

  ---

  I have a fresh Bionic install with DI which doesn't mention netplan in
  ENI:

  $ more interfaces
  # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
  # Generated by debian-installer.

  # The loopback interface
  auto lo
  iface lo inet loopback

  This is particularly confusing since ifupdown is not installed :)

  I think this file wants to say that netplan is installed by default,
  ifupdown is still available if needed, and where to go for more
  information.

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