64-char hostname causes dhcp server to reject lease
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Dan Streetman |
Bug 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/
[Match]
Name=ens3
[Network]
DHCP=yes
set hostname to 64-char name, e.g.:
$ sudo hostnamectl set-hostname a123456789b1234
restart networkd:
$ sudo systemctl restart systemd-networkd
check logs:
root@a123456789
May 06 19:01:30 a123456789b1234
[regression potential]
Any regression would likely result in failure configuring/
[scope]
this is fixed by commit 9740eae694e93b0
[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.
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Xenial): | |
assignee: | nobody → Dan Streetman (ddstreet) |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
Hello Dan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ systemd/ 229-4ubuntu21. 29 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.