Description of problem: http://www.forums.fedoraforum.org/showpost.php?p=1788484&postcount=8 Version-Release number of selected component (if applicable): 4.11.3-302.fc26.x86_64 <<=== NEWLY INSTALLED 4.11.3-300.fc26.x86_64 4.11.2-300.fc26.x86_64 <<=== INVISIBLE (some entity keeps track of it)??? 4.11.1-300.fc26.x86_64 <<=== DEINSTALLED! How reproducible: Still in affect Actual results: I see ONLY two kernels in GRUB2 boot menu?! 4.11.3-302.fc26.x86_64 <<=== NEWLY INSTALLED 4.11.3-300.fc26.x86_64 Expected results: 4.11.3-302.fc26.x86_64 <<=== NEWLY INSTALLED 4.11.3-300.fc26.x86_64 4.11.2-300.fc26.x86_64
I managed to find where rpm stores the update database: http://www.forums.fedoraforum.org/showpost.php?p=1788596&postcount=12 So even kernel 4.11.2-300.fc26.x86_64 does NOT have representatives in /boot: [root@localhost boot]# ls -al total 124880 dr-xr-xr-x. 8 root root 4096 Jun 7 06:26 . dr-xr-xr-x. 18 root root 4096 Mar 29 21:20 .. drwxr-xr-x. 6 root root 4096 Jun 7 06:26 5a76d41d758649feb94e3abdbfa7157f -rw-r--r--. 1 root root 185326 May 25 21:00 config-4.11.3-300.fc26.x86_64 -rw-r--r--. 1 root root 185315 Jun 5 20:59 config-4.11.3-302.fc26.x86_64 drwxr-xr-x. 3 root root 4096 Mar 29 21:23 dbed1a205afe4fd3b60050c0e205222f drwx------. 4 root root 4096 Mar 29 21:23 efi -rw-r--r--. 1 root root 184380 Feb 11 06:58 elf-memtest86+-5.01 drwxr-xr-x. 2 root root 4096 Mar 29 21:21 extlinux drwxr-xr-x. 6 root root 4096 Jun 7 06:26 grub2 -rw-------. 1 root root 56980221 May 14 19:54 initramfs-0-rescue-5a76d41d758649feb94e3abdbfa7157f.img -rw-------. 1 root root 20570156 May 27 09:42 initramfs-4.11.3-300.fc26.x86_64.img -rw-------. 1 root root 20571538 Jun 7 06:26 initramfs-4.11.3-302.fc26.x86_64.img drwx------. 2 root root 16384 May 14 19:50 lost+found -rw-r--r--. 1 root root 182704 Feb 11 06:58 memtest86+-5.01 -rw-------. 1 root root 3549687 May 25 21:00 System.map-4.11.3-300.fc26.x86_64 -rw-------. 1 root root 3549687 Jun 5 20:59 System.map-4.11.3-302.fc26.x86_64 -rwxr-xr-x. 1 root root 7262808 May 14 19:54 vmlinuz-0-rescue-5a76d41d758649feb94e3abdbfa7157f -rwxr-xr-x. 1 root root 7282776 May 25 21:01 vmlinuz-4.11.3-300.fc26.x86_64 -rw-r--r--. 1 root root 167 May 25 20:56 .vmlinuz-4.11.3-300.fc26.x86_64.hmac -rwxr-xr-x. 1 root root 7282776 Jun 5 21:00 vmlinuz-4.11.3-302.fc26.x86_64 -rw-r--r--. 1 root root 167 Jun 5 20:53 .vmlinuz-4.11.3-302.fc26.x86_64.hmac [root@localhost boot]# It does exist in rpm local database: [root@localhost log]# dnf list installed | grep kernel abrt-addon-kerneloops.x86_64 2.10.2-2.fc26 @updates-testing kernel.x86_64 4.11.2-300.fc26 @updates-testing kernel.x86_64 4.11.3-300.fc26 @updates-testing kernel.x86_64 4.11.3-302.fc26 @updates-testing kernel-core.x86_64 4.11.2-300.fc26 @System kernel-core.x86_64 4.11.3-300.fc26 @updates-testing kernel-core.x86_64 4.11.3-302.fc26 @updates-testing kernel-devel.x86_64 4.11.2-300.fc26 @System kernel-devel.x86_64 4.11.3-300.fc26 @updates-testing kernel-devel.x86_64 4.11.3-302.fc26 @updates-testing kernel-headers.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules.x86_64 4.11.2-300.fc26 @System kernel-modules.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.2-300.fc26 @System kernel-modules-extra.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.3-302.fc26 @updates-testing libreport-plugin-kerneloops.x86_64 2.9.1-2.fc26 @updates-testing [root@localhost log]# _______ The question is: why installation of kernel 4.11.2-300.fc26.x86_64 abruptly/violently exited, not finishing obvious installation to the /boot directory??? Few possible reasons for that: [1] Kernel 4.11.2-300.fc26.x86_64 scrip-let had fatal error? [2] mkinitrd script had fatal error? [3] You, Fedora 26 kernel maintainers, name other reason(s)??? Thank you, _nobody_
Other people also reported this failure. Here: http://www.forums.fedoraforum.org/showpost.php?p=1788676&postcount=8 Waiting for answers. _nobody_
Duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1443415 _nobody_
*** This bug has been marked as a duplicate of bug 1443415 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days