| 2020-05-06 19:35:58 |
Dan Streetman |
bug |
|
|
added bug |
| 2020-05-06 19:36:05 |
Dan Streetman |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-05-06 19:36:05 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2020-05-06 19:36:11 |
Dan Streetman |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2020-05-06 19:36:13 |
Dan Streetman |
systemd (Ubuntu Xenial): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-05-06 19:36:15 |
Dan Streetman |
systemd (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2020-05-06 19:36:18 |
Dan Streetman |
systemd (Ubuntu Xenial): status |
New |
In Progress |
|
| 2020-05-29 16:26:56 |
Dan Streetman |
description |
[impact]
a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request.
[test case]
$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=yes
set hostname to 64-char name, e.g.:
$ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123
restart networkd:
$ sudo systemctl restart systemd-networkd
check logs:
root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument
[scope]
this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial.
[other info]
this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. |
[impact]
a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request.
[test case]
$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=yes
set hostname to 64-char name, e.g.:
$ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123
restart networkd:
$ sudo systemctl restart systemd-networkd
check logs:
root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument
[regression potential]
Any regression would likely result in failure configuring/processing dhcpv4 server response, or rejection from the dhcpv4 server.
[scope]
this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial.
[other info]
this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. |
|
| 2020-09-04 08:32:11 |
Łukasz Zemczak |
systemd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-09-04 08:32:12 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-09-04 08:32:13 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-09-04 08:32:15 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-xenial |
|
| 2020-09-09 18:48:04 |
Dan Streetman |
tags |
verification-needed verification-needed-xenial |
verification-done verification-done-xenial |
|
| 2020-09-15 16:16:33 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2020-09-15 16:16:56 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
