kdump-tools is unable to resolve DNS when systemd-resolved is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
makedumpfile (Ubuntu) |
Fix Released
|
Medium
|
Guilherme G. Piccoli | ||
Bionic |
Fix Released
|
Medium
|
Guilherme G. Piccoli | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Medium
|
Guilherme G. Piccoli | ||
Focal |
Fix Released
|
Medium
|
Guilherme G. Piccoli |
Bug Description
[Impact]
* Currently kdump is unable to handle domain name resolution due to the lack of "resolved" service in the kdump environment; this happens given the nature of reduced service load required in the kdump scenario.
* Kdump currently relies on a systemd service approach - there are 2 services, one being a configuration/load entity (kdump-
* The systemd DNS tool ("resolved") is not ready in the moment kdump-tools-dump service is up to collect the kernel dump; also, "resolved" depends on dbus.socket to work, so to have a fully functional DNS resolution we are hereby adding both services as dependencies for kdump-tools-dump, so the network dump functionality works with hostnames (not requiring anymore that users set IP raw addresses).
* The attached SVG files (kdump.svg and regular_boot.svg) contains "systemd-analyze plot" outputs from a kdump-tools-dump and regular boot perspective. To collect the kdump data we manage to change the kdump-tools-dump service to load SSHd and also that required disabling the OneShot property of such service. With that data, one can check the services started/completed in each environment - it's possible to notice the absence of systemd-resolved when in kdump environment.
* Notice this modification is being worked concurrently with other kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure a network dump (SSH or NFS) using hostnames for the target machine;
5) Perform the test dump (with 'echo c> /proc/sysrq-
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained to kdump-tools package; it'll only affect the services loaded before kdump-tools-dump collecting service.
A regression would then potentially fails kdump completion if one of the new services added to the kdump environment load (resolved and dbus.socket) fails to load and stalls/prevents the kdump service complete load.
Changed in makedumpfile (Ubuntu Disco): | |
status: | Won't Fix → In Progress |
Changed in makedumpfile (Ubuntu Eoan): | |
status: | Confirmed → In Progress |
Changed in makedumpfile (Ubuntu Focal): | |
status: | Confirmed → In Progress |
Changed in makedumpfile (Ubuntu Bionic): | |
status: | Confirmed → In Progress |
Changed in makedumpfile (Ubuntu Disco): | |
status: | In Progress → Won't Fix |
importance: | Low → Undecided |
assignee: | Guilherme G. Piccoli (gpiccoli) → nobody |
Disco soon to be retired (in favor of Eoan) - given that the impact of this bug is medium to low, we won't apply the future changes to Disco.