[Bug 1708409] Re: kdump service does not start after configure/reboot

[Steve Langasek]

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
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1708409

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram <hasriram at in.ibm.com> - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  ----Additional Info-----
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres
     Active: inactive (dead)

  ...........................
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions