[Bug 1738998] Re: netplan does not allow dhcp client identifier type to be specified

[Launchpad Bug Tracker]

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

---------------
nplan (0.32~16.04.5) xenial; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
    "mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * Do not attempt to rebind driver 'qeth'. (LP: #1756322)
  * Allow setting ClientIdentifier=mac for networkd-renderered devices
    (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
10:36:24 -0400

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

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

Title:
  netplan does not allow dhcp client identifier type to be specified

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Users of Ubuntu dealing with a DHCP server based on Windows Server, Solarwinds IPAM, or possibly other DHCP server products that do no support RFC 4361.

  [Test case]
  -- requires a Windows Server DHCP setup, or another product without support for client identifier DUIDs.

  1) Configure a reservation for the device, using the device's MAC address.
  2) Configure the device for DHCP:

  network:
    version: 2
    renderer: networkd
    ethernets:
      eth0:
        dhcp4: yes
        dhcp-identifier: mac

  3) Run 'netplan apply'
  4) Verify that 'netplan apply' completes successfully, and that the expected IP address is received as part of the reservation. It may be required to clear the DHCP server's cache of DHCP requests/responses.

  [Regression potential]
  These DHCP behavior changes may lead to systems not receiving the same IP as they previously did on reservations from a DHCP server; the default is not changing from using DUIDs so unchanged configurations should not be affected at all, but changes to add the new feature will likely change the IP address returned to the client from the DHCP server. Additionally, failure to parse netplan configuration or invalid DHCP behavior should be investigated as possible regressions coming from this SRU.

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