http://bugzilla.suse.com/show_bug.cgi?id=1171180 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |guillaume.gardet@arm.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1171180 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1162581 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1171180 http://bugzilla.suse.com/show_bug.cgi?id=1171180#c3 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(schwab@suse.com) --- Comment #3 from Guillaume GARDET --- (In reply to Andreas Schwab from comment #2)

# get_kernel_version /boot/zImage-5.6.8-1-default ; echo $? 1 panda:~/:[0]# get_kernel_version /boot/vmlinux-5.6.8-1-default.xz ; echo $? 5.6.8-1-default 0

Partially fixed then.

panda:~/:[0]# mkinitrd No kernel found in /boot or bad modules dir in /lib/modules

Any reason you do not use 'dracut' instead of mkinitrd? Could you try 'dracut' instead, please? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1171180 http://bugzilla.suse.com/show_bug.cgi?id=1171180#c5 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.molkentin@suse.com, | |thomas.blume@suse.com Flags| |needinfo?(schwab@suse.com) --- Comment #5 from Guillaume GARDET --- (In reply to Andreas Schwab from comment #4)

Because that's what everyone is using.

mkinitrd is just a wrapper around dracut. On kernel update, dracut is used nowadays. @Andreas, could you confirm that dracut is working properly, please? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c7 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |fvogt@suse.com --- Comment #7 from Fabian Vogt --- I see this issue as well. As written in comment 6, mkinitrd is still used to regenerate the initrd on package updates. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c10 --- Comment #10 from Dirk Mueller --- I guess that patch is reversed, right? the other option is to fix our kernel image name to no longer be called zImage, but instead similar to all other distributions inherit the x86 name. this might be not so difficult to pull off, and it fixes dracut and all other occurences where we need to fix stuff (I remember other unfixed cases in virtualization and containerization area). I would prefer that over finding more places to hack. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c14 --- Comment #14 from Michal Suchanek --- Why does it not work? The code seems to match zImage: default_kernel_images() { local regex kernel_image kernel_version version_version initrd_image local qf='%{NAME}-%{VERSION}-%{RELEASE}\n' case "${DRACUT_ARCH:-$(uname -m)}" in s390|s390x) regex='image' ;; ppc|ppc64) regex='vmlinux' ;; i?86|x86_64) regex='vmlinuz' ;; arm*) regex='[uz]Image' ;; aarch64|riscv64) regex='Image' ;; *) regex='vmlinu.' ;; esac -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c16 --- Comment #16 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_minimalx https://openqa.opensuse.org/tests/1838553 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c18 --- Comment #18 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_minimalx https://openqa.opensuse.org/tests/1876432 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1171180 https://bugzilla.suse.com/show_bug.cgi?id=1171180#c20 --- Comment #20 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_in_textmode https://openqa.opensuse.org/tests/1913292 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.