resolved dhclient-enter-hook complains about an empty file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Low
|
Dan Streetman | ||
Focal |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[impact]
When starting/using `dhclient`, it will often return an error such as:
cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty
[test case]
run dhclient for the first time (for the current boot) on a bionic/focal system, or remove the file(s) in /run/systemd/
[regression potential]
any regression would likely cause the DNS configuration that dhclient gets to not be properly reported to systemd-resolved, resulting in problematic/broken systemd DNS resolution.
[scope]
this is needed in b/f
this hook was removed from systemd starting in g, and the hook was not yet added in x, so this change is needed only in b and f.
[original description]
When starting/using `dhclient`, it will often return an error such as:
cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty
This is due to the use of `cmp` in "/etc/dhcp/
Because the $oldstate file can be empty, or different, it should use `cmp --quiet`
This happens when "/run/systemd/
This is very loosely related to https:/
description: | updated |
Changed in systemd (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Focal): | |
importance: | Undecided → Low |
Changed in systemd (Ubuntu Bionic): | |
importance: | Medium → Low |
status: | New → In Progress |
Changed in systemd (Ubuntu Focal): | |
status: | New → In Progress |
Status changed to 'Confirmed' because the bug affects multiple users.