This bug was fixed in the package linux-base - 4.5ubuntu3.5
---------------
linux-base (4.5ubuntu3.5) focal; urgency=medium
* Rewrite xx-update-initrd-links to use linux-update-symlinks. This will
now make installkernel behaviour match the linux-image-*.postinst
behaviour exactly with respect to creating & updating vmlinu? and
initrd.img symlinks in / or /boot. LP: #1929255
linux-base (4.5ubuntu3.4) focal; urgency=medium
* Check for update-initramfs being installed before running the postinst
hook which updates the softlinks (LP: #1928700).
linux-base (4.5ubuntu3.3) focal; urgency=medium
* Make the new posinst hook executable (the correct bits were lost when
adding the scripts via debdiff) (LP: #1877088).
linux-base (4.5ubuntu3.2) focal; urgency=medium
[ Stefan Bader ]
* Add kernel postinst hook to update initrd softlinks to match the kernel
version targets (LP: #1877088).
-- Dimitri John Ledkov <[email protected]> Wed, 02 Jun 2021 09:43:06
+0100
** Changed in: linux-base (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux-base (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1877088
Title:
[UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
which is required with the default zipl.conf
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux-base package in Ubuntu:
Fix Released
Status in linux-base source package in Bionic:
Fix Released
Status in linux-base source package in Focal:
Fix Released
Status in linux-base source package in Hirsute:
Fix Released
Bug description:
[Impact]
* initrd link is not updated when using installkernel or "make
install" from kernel sources. This leads to boot failure after
installing a new kernel with mentioned methods because the kernel does
not match initrd.
* It's a regression because for Focal it was working before.
* Issue was reproduced also on Bionic.
* The proposed fixed by Stefan Bader adds a hook in
/etc/kernel/postinst.d/ so installkernel will relink the initrd. The
kernel DEB packages should not be affected.
* The solution from Stefan (first patch) was tested by the bug
reporter ([email protected]).
[Test Plan]
* Build a kernel
* sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
* Check if /boot/initrd or /initrd symlink to the new initrd
[Where problems could occur]
* Installing kernel via: installkernel or "make install", so mostly
kernel developer environments
[Other info from developer]
When testing development kernels I usually rely on the installkernel
script either through the "make install" target of the Kernel source
or manually. This used to work great on Ubuntu on Z.
On Ubuntu 20.04 (freshly installed up to date) this fails however because
/boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
wrong kernel/initrd combination rendering the system unbootable.
(with the correct modules already copied to
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
# sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dasda (3844).
Done.
run-parts: executing /etc/kernel/postinst.d/zz-zipl
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dasda (3844).
Done.
# ls -l /boot
total 178364
-rw------- 1 root root 135168 May 6 11:52 bootmap
-rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
lrwxrwxrwx 1 root root 27 May 6 11:40 initrd.img ->
initrd.img-5.4.0-29-generic <====== should point to new version
-rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic
-rw-r--r-- 1 root root 125339494 May 6 11:52
initrd.img-5.7.0-rc4-06500-gb67ea026badd
lrwxrwxrwx 1 root root 27 May 6 11:40 initrd.img.old ->
initrd.img-5.4.0-29-generic
-rw------- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic
-rw-r--r-- 1 root root 4031691 May 6 11:52
System.map-5.7.0-rc4-06500-gb67ea026badd
-rw-r--r-- 1 root root 4031691 May 6 11:49
System.map-5.7.0-rc4-06500-gb67ea026badd.old
lrwxrwxrwx 1 root root 37 May 6 11:52 vmlinuz ->
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
-rw------- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
-rw-r--r-- 1 root root 9080832 May 6 11:52
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
-rw-r--r-- 1 root root 9080832 May 6 11:49
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
lrwxrwxrwx 1 root root 41 May 6 11:52 vmlinuz.old ->
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
