Ubuntu
kdump-tools package

[UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)

Bug #1982582 reported by bugproxy on 2022-07-22

This bug affects 1 person

	Status	Importance	Assigned to
Ubuntu on IBM z Systems	Fix Released	High	Skipper Bug Screeners
kdump-tools (Ubuntu)	Fix Released	High	Unassigned
Jammy	Fix Released	Undecided	Unassigned
Kinetic	Fix Released	Undecided	Unassigned
Lunar	Fix Released	High	Unassigned

Bug Description

SRU Justification:
==================

[ Impact ]

* Unable to install the kdump-tools package in Jammy (or newer),
neither on LPARs, nor on z/VM guests.

* The issue is in debian/kdump-tools.postinst, function 'update_zipl()',
where there is a '--debconf-ok' argument missing for ucf.

[ Fixes ]

* Add argument '--debconf-ok' to ucf call in 'update_zipl()' in the
kdump-tools postinst script.

[ Test Plan ]

* Have an Ubuntu Server on s390x (Jammy or newer) installation
on LPAR and z/VM and install the kdump-tools package with:
sudo apt install kdump-tools

* The broken package fails with an error message like this:
   "ErrorMessage:
    installed kdump-tools package post-installation script subprocess
    returned error exit status 2
    ...
    Setting up kdump-tools (1:1.6.10ubuntu1) ...
    *** WARNING: ucf was run from a maintainer script that uses debconf, but
              the script did not pass --debconf-ok to ucf. The maintainer
              script should be fixed to not stop debconf before calling ucf,
              and pass it this parameter. For now, ucf will revert to using
              old-style, non-debconf prompting. Ugh!

    Please inform the package maintainer about this problem.
    Need debconf to interact 'dpkg' error processing package kdump-tools (--configure):
    installed kdump-tools package post-installation script subprocess
    returned error exit status 2"

* The fixes package will just flawlessly install.

[ Where problems could occur ]

* It's just a one line change adding the argument '--debconf-ok' to ucf;
like in other occurrences in the postinst script.

* So the change is fortunately very traceable.

* If done at a wrong spot, it may accidentally indicate that it's ok for ucf
to use an existing debconf instance for prompting, even if not desired.

* It can cuase issue with maintainer scripts that used debconf where
ucf had to disable/cripple debconf before running ucf.

* The argument tells the maintainer script that it's safe to use debconf,
even when the script discovers that debconf is already running.
__________

Unable to install kdump-tools on 22.04 (Jammy) on s390x (LPAR nor z/VM guest)
Errors were encountered while processing:
kdump-tools
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Contact Information = Vanessa <email address hidden>

---uname output---
Linux ilzlnx15 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:22:27 UTC 2022 s390x s390x s390x GNU/Linux

Machine Type = s390x

---Debugger---
A debugger is not configured

---Steps to Reproduce---
apt-get install kdump-tools
or
apt-get install linux-crashdump

== Comment: #1 - Ruth Vanessa Baeza Elizalde <email address hidden> - 2022-07-21 14:09:21 ==

== Comment: #6 - Steffen Maier <email address hidden> - 2022-07-22 06:15:06 ==
(In reply to comment #1)
> Created attachment 155027 [details]
> sosreport-ilzlnx15-199072-2022-07-21-cpplakh

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat sos_commands/kdump/kdump-config_show
* /etc/default/kdump-tools: USE_KDUMP is not set or zero
* no crashkernel= parameter in the kernel cmdline

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat ./proc/cmdline
root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat etc/zipl.conf
# This has been modified by the MAAS curtin installer
[defaultboot]
default=ubuntu
[ubuntu]
target = /boot
image = /boot/vmlinuz
ramdisk = /boot/initrd.img
parameters = root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH

Looks like some preconditions for kdump are not fulfilled.
[https://ubuntu.com/server/docs/kernel-crash-dump]
Are those supposed to be created by the installation of kdump-tools or does that package require those pre-reqs to already be fulfilled to get installed? (I'm not familiar with kdump tooling on Ubuntu.)
Vanessa, is this different from previous Ubuntu versions you deployed? (cf. bug 194306)

FYI, there's also this known kdump bug 195646.

While kdump is really nice, you could continue with just a working standalone dump for the time being in order not to jeopardize your schedules.

(In reply to comment #0)
> ---Problem Description---
> Unable to install kdump-tools on 22.04 (Jammy Jellyfish) on s390x (LPAR nor
> zVM guest)
> Errors were encountered while processing:
> kdump-tools
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Are there any more details on the error it faced?
Copy&paste from the terminal? (issued command and its output)

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ fgrep kdump var/log/dpkg.log
465:2022-07-21 10:48:56 install kdump-tools:s390x <none> 1:1.6.10ubuntu1
467:2022-07-21 10:48:56 status half-installed kdump-tools:s390x 1:1.6.10ubuntu1
468:2022-07-21 10:48:56 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1
489:2022-07-21 10:49:05 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
490:2022-07-21 10:49:05 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1
491:2022-07-21 10:49:05 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
502:2022-07-21 10:54:06 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
504:2022-07-21 10:54:06 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
509:2022-07-21 11:04:42 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
510:2022-07-21 11:04:43 remove kdump-tools:s390x 1:1.6.10ubuntu1 <none>
512:2022-07-21 11:04:43 status half-installed kdump-tools:s390x 1:1.6.10ubuntu1
514:2022-07-21 11:04:46 status config-files kdump-tools:s390x 1:1.6.10ubuntu1
523:2022-07-21 11:06:45 install kdump-tools:s390x 1:1.6.10ubuntu1 1:1.6.10ubuntu1
525:2022-07-21 11:06:45 status half-installed kdump-tools:s390x 1:1.6.10ubuntu1
527:2022-07-21 11:06:45 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1
532:2022-07-21 11:06:45 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
533:2022-07-21 11:06:45 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1
534:2022-07-21 11:06:45 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
548:2022-07-21 11:08:27 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
550:2022-07-21 11:08:27 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
784:2022-07-21 11:14:25 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
785:2022-07-21 11:14:25 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
904:2022-07-21 11:16:19 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
906:2022-07-21 11:16:19 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
917:2022-07-21 11:16:43 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
919:2022-07-21 11:16:43 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
924:2022-07-21 11:16:57 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
926:2022-07-21 11:16:57 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
935:2022-07-21 11:17:51 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
937:2022-07-21 11:17:51 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
942:2022-07-21 11:19:55 configure kdump-tools:s390x 1:1.6.10ubuntu1 <none>
944:2022-07-21 11:19:55 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1
^^^^^^^^^^^^^^

I suppose those caused the following incomplete left-overs:

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](2)$ l ./etc/default/kdump-tools.*
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.2WRFKv
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.6EWiZz
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.DHxhm1
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.GvHOGR
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.HwReC4
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.N8ci1Z
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.rfe3y9
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.Rzpckn
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.wlDTYt
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/kdump-tools.xH9wMJ

but no final ./etc/default/kdump-tools likely due to the package install error.

Could not find anything about kdump in apt logs within sosreport.

== Comment: #7 - Steffen Maier <email address hidden> - 2022-07-22 06:58:42 ==
(In reply to comment #6)
> (In reply to comment #1)
> > Created attachment 155027 [details]
> > sosreport-ilzlnx15-199072-2022-07-21-cpplakh

> Could not find anything about kdump in apt logs within sosreport.

Oh yeah, sosreport contains pipe/fifo files so a simple recursive grep just blocks forever once it hits on of those special files. Jumping through hoops:

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ find -type f -print0 | xargs -0 -n1 fgrep -Hi kdump

[maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](123)$ zless ./var/log/apt/term.log*

Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-tools_1%3a1.6.10ubuntu1_s390x.deb ...
Unpacking kdump-tools (1:1.6.10ubuntu1) ...
Selecting previously unselected package libdw1:s390x.
Preparing to unpack .../libdw1_0.186-1build1_s390x.deb ...
Unpacking libdw1:s390x (0.186-1build1) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfile_1%3a1.7.0-1build1_s390x.deb ...
Unpacking makedumpfile (1:1.7.0-1build1) ...
Setting up libdw1:s390x (0.186-1build1) ...
Setting up makedumpfile (1:1.7.0-1build1) ...
Setting up kexec-tools (1:2.0.22-2ubuntu2) ...
Generating /etc/default/kexec...
Setting up kdump-tools (1:1.6.10ubuntu1) ...
*** WARNING: ucf was run from a maintainer script that uses debconf, but
             the script did not pass --debconf-ok to ucf. The maintainer
             script should be fixed to not stop debconf before calling ucf,
             and pass it this parameter. For now, ucf will revert to using
             old-style, non-debconf prompting. Ugh!

Please inform the package maintainer about this problem.
Need debconf to interact
ESC[1mdpkg:ESC[0m error processing package kdump-tools (--configure):
installed kdump-tools package post-installation script subprocess returned error exit status 2
Processing triggers for libc-bin (2.35-0ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for initramfs-tools (0.140ubuntu13) ...
Errors were encountered while processing:
kdump-tools
Log ended: 2022-07-21 10:49:05

>>> repeats for all the install attempts <<<

Unfortunately, it does not show the post-installation script or its error and I don't know how to show the script or increase debugging for .deb packages.

Log started: 2022-07-21 11:19:55
Setting up kdump-tools (1:1.6.10ubuntu1) ...
*** WARNING: ucf was run from a maintainer script that uses debconf, but
             the script did not pass --debconf-ok to ucf. The maintainer
             script should be fixed to not stop debconf before calling ucf,
             and pass it this parameter. For now, ucf will revert to using
             old-style, non-debconf prompting. Ugh!

Please inform the package maintainer about this problem.
Need debconf to interact
dpkg: error processing package kdump-tools (--configure):
installed kdump-tools package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of linux-crashdump:
linux-crashdump depends on kdump-tools; however:
Package kdump-tools is not configured yet.

dpkg: error processing package linux-crashdump (--configure):
dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic
Using config file '/etc/zipl.conf'
Run /lib/s390-tools//zipl_helper.device-mapper /boot
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: dm-7.
Done.
Errors were encountered while processing:
kdump-tools
linux-crashdump
Log ended: 2022-07-21 11:19:58

See original description

Tags:

Revision history for this message

bugproxy (bugproxy) wrote on 2022-07-22: sosreport-ilzlnx15-199072-2022-07-21-cpplakh

sosreport-ilzlnx15-199072-2022-07-21-cpplakh Edit (15.5 MiB, application/x-xz)

Default Comment by Bridge

tags:	added: architecture-s39064 bugnameltc-199072 severity-high targetmilestone-inin---
Changed in ubuntu:
assignee:	nobody → Skipper Bug Screeners (skipper-screen-team)
affects:	ubuntu → linux (Ubuntu)

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-07-22:

crash file Edit (109.6 KiB, text/html)

I can confirm and recreate this problem.

It's a problem with the kdump-tools post-inst script:
"
ErrorMessage:
installed kdump-tools package post-installation script subprocess returned error exit status 2
...
Setting up kdump-tools (1:1.6.10ubuntu1) ...^M
*** WARNING: ucf was run from a maintainer script that uses debconf, but^M
              the script did not pass --debconf-ok to ucf. The maintainer^M
              script should be fixed to not stop debconf before calling ucf,^M
              and pass it this parameter. For now, ucf will revert to using^M
              old-style, non-debconf prompting. Ugh!^M
^M
              Please inform the package maintainer about this problem.^M
Need debconf to interact^M
^[[1mdpkg:^[[0m error processing package kdump-tools (--configure):^M
  installed kdump-tools package post-installation script subprocess returned error exit status 2^M
"

affects:	linux (Ubuntu) → kdump-tools (Ubuntu)
Changed in kdump-tools (Ubuntu):
assignee:	Skipper Bug Screeners (skipper-screen-team) → Canonical Kernel Team (canonical-kernel-team)
Changed in ubuntu-z-systems:
assignee:	nobody → Skipper Bug Screeners (skipper-screen-team)
Changed in kdump-tools (Ubuntu):
importance:	Undecided → High
Changed in ubuntu-z-systems:
importance:	Undecided → High
Changed in kdump-tools (Ubuntu):
status:	New → Confirmed
Changed in ubuntu-z-systems:
status:	New → Confirmed

Revision history for this message

bugproxy (bugproxy) wrote on 2022-11-23: Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2022-11-23 05:44 EDT-------
@Canonical, any updates here?
Same problem on 22.04.1, as expected.

Revision history for this message

dann frazier (dannf) wrote on 2022-11-23:

@fheimes - does simply adding --debconf-ok in the ucf call in debian/kdump-tools.postinst:update_zipl() fix the issue for you?

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-11-23:

successful_test.txt Edit (6.9 KiB, text/plain)

Hi dannf, yes, I think that is the missing bit.

I've did a PPA build of a modified 'kdump-tools' package for lunar, that is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1982582/+packages
That I was able to successfully test on lunar/s390x.
I've attached my test run here.

I'll now work on a debdiff...

Changed in kdump-tools (Ubuntu):
status:	Confirmed → In Progress
Changed in ubuntu-z-systems:
status:	Confirmed → In Progress

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-11-23:

Now uploading the debdiffs for lunar, kinetic and jammy.
(Further builds are still running, adding K and J.)

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-11-23:

debdiffs.tgz Edit (936 bytes, application/x-tar)

Frank Heimes (fheimes) on 2022-11-23

Changed in kdump-tools (Ubuntu):
assignee:	Canonical Kernel Team (canonical-kernel-team) → nobody

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-11-25:

Since the builds for Jammy and Kinetic completed successfully,
I tested these packages on their corresponding Ubuntu releases
and didn't came across this issues anymore.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-11-28:

This bug was fixed in the package kdump-tools - 1:1.8ubuntu2

---------------
kdump-tools (1:1.8ubuntu2) lunar; urgency=medium

* Modifed ucf call in d/kdump-tools.postinst to use option
'--debconf-ok' to fix a package install issue (LP: #1982582).

-- Frank Heimes <email address hidden> Wed, 23 Nov 2022 19:40:57 +0100

Changed in kdump-tools (Ubuntu Lunar):
status:	In Progress → Fix Released

Frank Heimes (fheimes) on 2022-12-01

description:

updated

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2022-12-02: Please test proposed package

#10

Hello bugproxy, or anyone else affected,

Accepted kdump-tools into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kdump-tools/1:1.8ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in kdump-tools (Ubuntu Kinetic):
status:	New → Fix Committed
tags:	added: verification-needed verification-needed-kinetic
Changed in kdump-tools (Ubuntu Jammy):
status:	New → Fix Committed
tags:	added: verification-needed-jammy

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2022-12-02:

#11

Hello bugproxy, or anyone else affected,

Accepted kdump-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kdump-tools/1:1.6.10ubuntu2.1 in a few hours, and then in the -proposed repository.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-12-02:

#12

kinetic_verification.txt Edit (6.7 KiB, text/plain)

I was able to successfully verify kdump-tools 1:1.8ubuntu1.1 on kinetic - see attachment.
Hence I'm adjusting the tag accordingly.

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-12-02:

#13

jammy_verification.txt Edit (4.4 KiB, text/plain)

I was able to successfully verify kdump-tools 1:1.6.10ubuntu2.1 on jammy - see attachment.
Hence I'm adjusting the tags accordingly.

tags:	added: verification-done verification-done-jammy verification-done-kinetic removed: verification-needed verification-needed-jammy verification-needed-kinetic
Changed in ubuntu-z-systems:
status:	In Progress → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-12-13:

#14

This bug was fixed in the package kdump-tools - 1:1.8ubuntu1.1

---------------
kdump-tools (1:1.8ubuntu1.1) kinetic; urgency=medium

* Modifed ucf call in d/kdump-tools.postinst to use option
'--debconf-ok' to fix a package install issue (LP: #1982582).

-- Frank Heimes <email address hidden> Wed, 23 Nov 2022 19:07:18 +0100

Changed in kdump-tools (Ubuntu Kinetic):
status:	Fix Committed → Fix Released

Revision history for this message

Brian Murray (brian-murray) wrote on 2022-12-13: Update Released

#15

The verification of the Stable Release Update for kdump-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-12-13:

#16

This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2.1

---------------
kdump-tools (1:1.6.10ubuntu2.1) jammy; urgency=medium

* Modifed ucf call in d/kdump-tools.postinst to use option
'--debconf-ok' to fix a package install issue (LP: #1982582).

-- Frank Heimes <email address hidden> Wed, 23 Nov 2022 19:12:58 +0100

Changed in kdump-tools (Ubuntu Jammy):
status:	Fix Committed → Fix Released

Frank Heimes (fheimes) on 2022-12-13

Changed in ubuntu-z-systems:
status:	Fix Committed → Fix Released

Revision history for this message

bugproxy (bugproxy) wrote on 2022-12-16: Comment bridged from LTC Bugzilla

#17

------- Comment From <email address hidden> 2022-12-16 08:38 EDT-------
I was also able to successfully verify unattended installation of kdump-tools 1:1.6.10ubuntu2.1 on jammy
However - but this might be a separate issue - there is not value for crashkernel memory set (which makes no sense and prevents kdump from dumping:

root@a3515006:~# systemctl status kdump-tools
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2022-12-16 13:16:35 UTC; 3min 13s ago
Process: 14751 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS)
Main PID: 14751 (code=exited, status=0/SUCCESS)
CPU: 12ms

Dec 16 13:16:35 a3515006.lnxne.boe systemd[1]: Starting Kernel crash dump capture service...
Dec 16 13:16:35 a3515006.lnxne.boe kdump-tools[14751]: Starting kdump-tools:
Dec 16 13:16:35 a3515006.lnxne.boe kdump-tools[14756]: * no crashkernel= parameter in the kernel cmdline
Dec 16 13:16:35 a3515006.lnxne.boe systemd[1]: Finished Kernel crash dump capture service.
root@a3515006:~# cat /proc/cmdline
root=/dev/disk/by-path/ccw-0.0.6b14-part1 BOOT_IMAGE=0
root@a3515006:~# cat /etc/zipl.conf

# This has been modified by the MAAS curtin installer
[defaultboot]
default=ubuntu

[ubuntu]
target = /boot
image = /boot/vmlinuz
ramdisk = /boot/initrd.img
parameters = root=/dev/disk/by-path/ccw-0.0.6b14-part1

root@a3515006:~#

The installation didn't set a crashkernel value in /etc/zipl.conf (like focal was doing). A triggered panic didn't create a kdump, unless I set the crashkernel parameter appropriately and rebooted.

Revision history for this message

Frank Heimes (fheimes) wrote on 2022-12-16:

#18

Hi Thorsten, umpf - yes, that's worth a separate bug.
(I only tested the installation issue that was initially reported.)
Since this bug is already closed, it's best to open a new/separate for the missing crashkernel setting.

bugproxy (bugproxy) on 2023-01-09

tags:

added: targetmilestone-inin2204
removed: targetmilestone-inin---

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntukdump-tools package

[UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
kdump-tools package