s390 missing dumpconf service

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu3

---------------
s390-tools (1.34.0-0ubuntu3) xenial; urgency=medium

  * Ship all tools, mostly harmless LP: #1555167, LP: #1564690, LP: #1564696
  * Add snmp build-dependency to build osasnmpd as a separate
    package LP: #1564699
  * Add cpuplugd, with patches to default config, as a separate
    package LP: #1564496
  * Update branding from "S/390" to "z Systems"

 -- Dimitri John Ledkov <email address hidden> Wed, 06 Apr 2016 02:12:04 +0100

------- Comment From <email address hidden> 2016-04-12 11:21 EDT-------
I couldn't start service named dumpconf still, with 1.34.0-0ubuntu4 version of s390-tools package:
root@s8330018:~# systemctl start dumpconf
Failed to start dumpconf.service: Unit dumpconf.service not found.
root@s8330018:~# systemctl status dumpconf
? dumpconf.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

Only man pages are related to dumpconf:
root@s8330018:~# dpkg -L s390-tools | grep dumpconf
/usr/share/man/man8/dumpconf.8.gz

root@s8330018:~# uname -a
Linux s8330018 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:06:05 UTC 2016 s390x s390x s390x GNU/Linux
root@s8330018:~# aptitude show s390-tools
Package: s390-tools
State: installed
Automatically installed: no
Version: 1.34.0-0ubuntu4
Priority: important
Section: admin
Maintainer: Ubuntu Developers <email address hidden>
Architecture: s390x
<...>

Hello,

dumpconf is not integrated properly upstream as far as I can see. It only ships /etc/sysconfig/dumpconf and it doesn't ship a systemd unit at all.

dumpconf needs to be integrated with systemd.

We would need to at least move dumpconf out of sysconfig, possibly. Or ship the init script as is. It's very odd that s390-tools doesn't ship systemd units for everything =/

------- Comment From <email address hidden> 2016-04-14 09:48 EDT-------
The dumpconf service is required for automatic dump mechanism for the s390
stand-alone dump tools. This has been very important before kdump has been
introduced.

These days with kdump importance of dumpconf is not so high any more.
Therefore we suggest to postpone integration of dumpconf.

Lower Severity from "Blocker" to "high"

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8

---------------
s390-tools (1.34.0-0ubuntu8) xenial; urgency=medium

  * Ship dumpconf legacy init script, and sysconfig file. LP: #1564690
  * Integrate ts-shell. LP: #1567473
  * Recommend statd package, and mention it by mon_statd name too to aid
    discovery.

 -- Dimitri John Ledkov <email address hidden> Thu, 14 Apr 2016 14:26:16 +0100

------- Comment From <email address hidden> 2016-05-04 04:23 EDT-------
Successful verification of fix within s390-tools (1.34.0-0ubuntu8) xenial.
dumpconf is available now:

# dpkg -l | grep s390-t
ii s390-tools 1.34.0-0ubuntu8 s390x

# systemctl start dumpconf

# systemctl status dumpconf
? dumpconf.service - LSB: Configure s390 dump feature
Loaded: loaded (/etc/init.d/dumpconf; bad; vendor preset: enabled)
Active: active (exited) since Wed 2016-05-04 10:19:20 CEST; 5s ago
Docs: man:systemd-sysv-generator(8)
Process: 55181 ExecStart=/etc/init.d/dumpconf start (code=exited, status=0/SUCCESS)

May 04 10:19:20 s83lp81 systemd[1]: Starting LSB: Configure s390 dump feature...
May 04 10:19:20 s83lp81 dumpconf[55181]: stop on panic configured.
May 04 10:19:20 s83lp81 systemd[1]: Started LSB: Configure s390 dump feature.