[Bug 1832042] Re: static ip= address configuration does not end up in netplan file

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.133ubuntu5

---------------
initramfs-tools (0.133ubuntu5) eoan; urgency=medium

  * Correctly serialize previously absent static ip configuration
    (declared as protocol 'none' by ipconfig) into runtime netplan
    yaml. LP: #1832042
  * Adjust testsuite sample file to match reality
  * Set executable bit on resume script in local-premount

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Fri, 07 Jun 2019 21:56:33
+0100

** Changed in: initramfs-tools (Ubuntu Eoan)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832042

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in initramfs-tools source package in Cosmic:
  New
Status in initramfs-tools source package in Disco:
  New
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

    ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

    Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+subscriptions