** Description changed: - Steps to reproduce + [Impact] + Users of Ubuntu dealing with a DHCP server based on Windows Server, possibly other DHCP server products that do no support RFC 4361. - 1. Go to man page for netplan - 2. search for "dhcp" - 3. Find only on/off options for dhcp4 and dhcp6 + [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.
** Description changed: [Impact] - Users of Ubuntu dealing with a DHCP server based on Windows Server, possibly other DHCP server products that do no support RFC 4361. + 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 + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738998 Title: netplan does not allow dhcp client identifier type to be specified To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1738998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
