https://bugzilla.suse.com/show_bug.cgi?id=1207703 https://bugzilla.suse.com/show_bug.cgi?id=1207703#c10 --- Comment #10 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Antonio Feijoo from comment #6)

This is not a dracut issue. A new grub entry should not be created if the initrd creation triggered by the kernel-default update fails.

That shouldn't happen, actually. Which version of suse-module-tools was installed when this problem occured? rpm-script only creates an entry in the boot menu if initrd-"$kernelrelease"-"$flavor" exists [1]. The "initrd" symlink is a different issue. Arguably, it should only be created if a new default boot entry is created, but currently, that part is independent, and is done earlier. This part could be fixed relatively easily. Recently, the entire process has become much more complicated, because we need to distinguish between grub and sd-boot installations, and transactional and non-transactional systems, and we have a completely different code flow for all of them. In general, it's hard to tell what the right course of action is if one of the multiple steps during the installation of a new kernel fails. It would seem reasonable to abort the entire transaction and restore the previous system state, but that's generally deprecated (rpm scriptlets are basically forbidden to exit with error status). [1] https://github.com/openSUSE/suse-module-tools/blob/503d772e6951ef8c268bc14f3... -- You are receiving this mail because: You are on the CC list for the bug.