Bug 18534

Summary:	Bootloader-config generates stand-alone initramdisk files for other distros (on grub2)
Product:	Mageia	Reporter:	Ulrich Beckmann <bequimao.de>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, zen25000
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakxtools	CVE:
Status comment:
Attachments:	Log from testcase CLI output with rpm -qa, ls -l /boot before and after test repeated test repeated Test on an actual Cauldron system

Description Ulrich Beckmann 2016-05-24 17:37:32 CEST

Description of problem:

I invoked in a fresh Mageia-6-sta1-x86_64-DVD install the script
# bootloader-config --action rebuild-initrds
It generates several initrd-files referring to long gone kernels.

Version-Release number of selected component (if applicable):


How reproducible:
I have seen this issue before. It should be reproducible.

Best regards,
Ulrich Beckmann

Comment 1 Ulrich Beckmann 2016-05-24 17:57:04 CEST

Created attachment 7849 [details]
Log from testcase

Comment 2 Barry Jackson 2016-05-25 15:47:18 CEST

Created attachment 7856 [details]
CLI output with rpm -qa, ls -l /boot before and after

Confirmed here in a rolling Cauldron installation - see attached.

CC: (none) => zen25000

Comment 3 Marja Van Waes 2016-05-25 22:16:44 CEST

I cannot reproduce this, but I saw Ulrich has an EFI system, I have legacy BIOS

I have 3 kernels (removed about 6 of them earlier today) and get only get initrd images for those three.

Besides, the line "Creating: target|kernel|dracut args|basicmodules" only appears once

Is there any chance this only happens on EFI systems?

Source RPM: draktools => drakxtools
CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Comment 4 Thierry Vignaud 2016-05-26 08:02:27 CEST

Barry, do your grub.cfg list those missing kernels?

Comment 5 Ulrich Beckmann 2016-05-26 08:29:23 CEST

Comment on attachment 7849 [details]
Log from testcase

Those are the kernels of other installation in a multi-boot system, probably extracted from grub.cfg. And not any extinct kernels. 

Thanks, Marja!

Ulrich

Comment 6 Barry Jackson 2016-05-26 15:24:08 CEST

(In reply to Thierry Vignaud from comment #4)
> Barry, do your grub.cfg list those missing kernels?

Update-grub2 output is still the same, finding only the installed kernels and not any of the newly created 'old' initrds

Generating grub configuration file ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-4.6.0-desktop-1.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-1.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc7.1.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc7.1.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.2.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.2.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.1.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.1.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.2.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.2.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.1.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.1.mga6.img
Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc4.1.mga6
Found initrd image: /boot/initrd-4.6.0-desktop-0.rc4.1.mga6.img
Found linux image: /boot/vmlinuz-4.4.6-desktop-1.mga6
Found initrd image: /boot/initrd-4.4.6-desktop-1.mga6.img
Found linux image: /boot/vmlinuz-4.4.5-desktop-1.mga6
Found initrd image: /boot/initrd-4.4.5-desktop-1.mga6.img
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found Mageia 5 (5) on /dev/sda4
Found Mageia 6 (6) on /dev/sda5
done

Comment 7 Thierry Vignaud 2016-05-26 15:44:54 CEST

What I meant is wether those removed kernels were still listed in grub.cfg _before_ you issued the rebuild command?

Severity: normal => minor
Keywords: (none) => NEEDINFO
Priority: Normal => Low

Comment 8 Barry Jackson 2016-05-26 15:58:51 CEST

Ah, I see your point - I cannot be 100% sure. I remember cleaning out a lot of old kernels a week or so ago, however with the bug that fails to run update-grub on kernel removal still with us, it is just possible that I did not check, or run it manually.

Comment 9 Ulrich Beckmann 2016-05-26 17:54:57 CEST

Created attachment 7862 [details]
test repeated

Hi, Thiery

I cleared /boot and repeated the test.

Best regards,
Ulrich

Comment 10 Thierry Vignaud 2016-05-26 18:53:01 CEST

So it read back grub2 config and tries to build initrds for other distros' kernels...

Summary: Bootloader-config generates stand-alone initramdisk files => Bootloader-config generates stand-alone initramdisk files for other distros (on grub2)

Comment 11 Ulrich Beckmann 2016-09-11 18:01:31 CEST

Created attachment 8400 [details]
test repeated

Just found out that the valid initrds are *not* rebuild.
This is a regression, and therefore I set the state to critical.

Ulrich

Ulrich Beckmann 2016-09-11 18:02:19 CEST

Priority: Low => Normal
Severity: minor => critical

Comment 12 Ulrich Beckmann 2017-03-29 17:36:15 CEST

Set severity to "normal". The script obviously is not used in any tools. Users may use the command mkinitrd to recreate their initramfs.

Severity: critical => normal

Marja Van Waes 2021-07-02 23:35:02 CEST

Keywords: NEEDINFO => (none)

Comment 13 Ulrich Beckmann 2021-07-05 21:02:32 CEST

Created attachment 12845 [details]
Test on an actual Cauldron system

I repeated the test on an actual Cauldron efi system.

Note that /boot is located on a btrfs subvolume and LVM, which is inhibited by the Mageia installer.

The error message 'Failed to find physical volume "/dev/sda7".'
can be neglected, no regression. It shows also in post install script of kernels. /dev/sda7 is a LUKS container.

As to the initramdisks, it does absolutely nothing.

Regards,
Ulrich