Bug 1394699

Summary: look in /lib/modules/$(uname -r)/ for kernel image first
Product: [Fedora] Fedora Reporter: Harald Hoyer <harald>
Component: superminAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: ptoscano, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: supermin-5.1.18-1.fc26 supermin-5.1.18-1.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-24 12:26:43 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:

Description Harald Hoyer 2016-11-14 09:37:51 UTC
Newer kernel-core packages package the kernel to in /lib/modules, so supermin should look for  /lib/modules/$(uname -r)/vmlinuz first before looking in /boot for the kernel image.

Comment 1 Pino Toscano 2016-11-14 09:45:02 UTC
Since when this change started? Also, are there compatibility symlinks in /boot?

Comment 2 Harald Hoyer 2016-11-16 12:47:28 UTC
/boot cannot carry symlinks in EFI environments.

Also, /boot/vmlinuz-$(uname -r) might not even exist, if someone is using a bootloader, which follows the bootloader specification.

kernel-install in kernel %post will install /lib/modules/$(uname -r)/vmlinuz to /boot ... location depends on the bootloader.

So, just look for /lib/modules/$(uname -r)/vmlinuz first and all should be fine.

Comment 3 Pino Toscano 2016-11-16 13:43:00 UTC
OK, I see.

One last question: is /lib/modules/$(uname -r)/vmlinuz always guaranteed to be unversioned, i.e. just "vmlinuz" no matter which arch/version/variant/etc?

Comment 4 Harald Hoyer 2016-11-16 14:06:35 UTC
(In reply to Pino Toscano from comment #3)
> OK, I see.
> 
> One last question: is /lib/modules/$(uname -r)/vmlinuz always guaranteed to
> be unversioned, i.e. just "vmlinuz" no matter which arch/version/variant/etc?

yes, because the version is already in the directory path

Comment 7 Fedora End Of Life 2017-02-28 10:36:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 8 Pino Toscano 2017-08-24 12:26:43 UTC
Other than what said already in comment 6, this is fixed in Fedora starting with the following packages:
- supermin-5.1.18-1.fc25
- supermin-5.1.18-1.fc26
- supermin-5.1.18-1.fc27