[UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
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/
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
and pass it this parameter. For now, ucf will revert to using
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-
[maier:
* /etc/default/
* no crashkernel= parameter in the kernel cmdline
[maier:
root=/dev/
[maier:
# 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/
Looks like some preconditions for kdump are not fulfilled.
[https:/
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:
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:
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
-rw-r--r--. 1 maier maier 4,5K 24. M?r 18:42 ./etc/default/
but no final ./etc/default/
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-
> 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:
[maier:
Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-
Unpacking kdump-tools (1:1.6.10ubuntu1) ...
Selecting previously unselected package libdw1:s390x.
Preparing to unpack .../libdw1_
Unpacking libdw1:s390x (0.186-1build1) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfil
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/
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
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
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.
Using config file '/etc/zipl.conf'
Run /lib/s390-
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
Changed in kdump-tools (Ubuntu): | |
assignee: | Canonical Kernel Team (canonical-kernel-team) → nobody |
description: | updated |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
tags: |
added: targetmilestone-inin2204 removed: targetmilestone-inin--- |
Default Comment by Bridge