Bug 2073734

Summary:	Kerneel not installed to /boot
Product:	[Fedora] Fedora	Reporter:	Harold Campbell <hcamp>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	acaringi, adscvr, airlied, alciregi, bskeggs, fedoraproject, filbranden, flepied, hdegoede, hpa, jarodwilson, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, lnykryn, masami256, mchehab, msekleta, ptalbert, ryncsn, ssahani, s, steved, systemd-maint, yuwatana, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-05 17:28:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Harold Campbell 2022-04-10 03:08:32 UTC

1. Please describe the problem:

Kernel does not get installed to /boot.

2. What is the Version-Release number of the kernel:

5.17.2-300.fc36.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

This started with whatever kernel was current when I upgraded to f36 beta.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Install or reinstall kernel(-core).

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes.

Running transaction
  Preparing        :                                                        1/1 
  Installing       : kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.   1/3 
  Running scriptlet: kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.   1/3 
  Installing       : kernel-modules-5.18.0-0.rc1.20220408git1831fed559732   2/3 
  Running scriptlet: kernel-modules-5.18.0-0.rc1.20220408git1831fed559732   2/3 
  Installing       : kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc   3/3 
  Running scriptlet: kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.   3/3 
kdump: kernel 5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 doesn't exist

  Running scriptlet: kernel-modules-5.18.0-0.rc1.20220408git1831fed559732   3/3 
  Running scriptlet: kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc   3/3 
  Verifying        : kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc   1/3 
  Verifying        : kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.   2/3 
  Verifying        : kernel-modules-5.18.0-0.rc1.20220408git1831fed559732   3/3 

Installed:
  kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64                 
  kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64            
  kernel-modules-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64         

Complete!

[root@kibble ~]# ls /boot
config-5.16.17-200.fc35.x86_64
efi
elf-memtest86+-5.31
extlinux
grub2
initramfs-0-rescue-313a6d6ebb9a489b92971a3db1877fe0.img
initramfs-5.16.17-200.fc35.x86_64.img
initrd-plymouth.img
loader
lost+found
memtest86+-5.31
symvers-5.16.17-200.fc35.x86_64.gz
System.map-5.16.17-200.fc35.x86_64
vmlinuz-0-rescue-313a6d6ebb9a489b92971a3db1877fe0
vmlinuz-5.16.17-200.fc35.x86_64
[root@kibble ~]# 




6. Are you running any modules that not shipped with directly Fedora's kernel?:

No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Harold Campbell 2022-04-10 03:09:11 UTC

I upgraded from f35 to f36 beta using the fedora-upgrade script.

Comment 2 Justin M. Forbes 2022-04-11 11:42:37 UTC

The kernel-install script handles this, which is a part of systemd. A few people seem to have run into this on using the dnf upgrade method (myself included on one system).  Can you please check /boot/efi/<machine-id> and see if the kernels were installed there?  Also of interest, do you know what version of Fedora this system was originally installed on?

Comment 3 Harold Campbell 2022-04-11 14:41:59 UTC

The kernel was indeed installed to /boot/efi/<machine-id>. Is /etc/machine-id the source of truth for that value?

My collection of backgrounds packages would suggest this system started life on f23.

Comment 4 Zbigniew Jędrzejewski-Szmek 2022-05-05 17:28:03 UTC


*** This bug has been marked as a duplicate of bug 2071034 ***