The referenced upstream bug report shows that upstream agrees this is a
regression in systemd behavior which they are planning to correct, which
is reasonable.
However, I think this is also a bug in the kdump-tools package.
'default.target' is a meta-target, which no package can know whether
it's appropriate to start its service under without knowing what
default.target is set to. In particular, kdump-tools also declares
'Wants=network-online.target'. If default.target (either on the kernel
commandline or on the filesystem) is pointed to some sort of local-only
rescue target, having network-online pulled into this target via kdump-
tools could break the boot.
I think kdump-tools in Debian and Ubuntu should instead be integrating
with multi-user.target.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Changed in: systemd (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Foundations Team (canonical-foundations)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708409
Title:
kdump service does not start after configure/reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
