Bug 2342379 - Error in dnf output involving kernel installation - recent change after rpm-ostree testing update caused some problems
Summary: Error in dnf output involving kernel installation - recent change after rpm-o...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-27 21:24 UTC by Brian Morrison
Modified: 2025-03-17 22:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-03-17 22:49:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brian Morrison 2025-01-27 21:24:23 UTC
I'm seeing this in dnf5 output, it's a new thing for this system and may have been provoked by rpm-ostree-2025.x packages from updates-testing (now reverted):

>>> Running post-transaction scriptlet: kernel-core-0:6.12.11-200.fc41.x86_64
>>> Non-critical error in post-transaction scriptlet: kernel-core-0:6.12.11-200.fc41.x86_64
>>> Scriptlet output:
>>> /usr/lib/kernel/install.d/51-dracut-rescue.install: line 91: /boot/efi/loader/entries/a0d5bf658c974a57b308adf730de0c4c-0-rescue.conf: No such file
>>> /usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 1.
>>> 
>>> [RPM] %posttrans(kernel-core-6.12.11-200.fc41.x86_64) scriptlet failed, exit status 1

the missing file shown exists, but in a different path at /boot/loader/entries/a0d5bf658c974a57b308adf730de0c4c-0-rescue.conf

It's not clear to me why this suddenly happened, but it seems once it has started occurring (broken kernel update with manual hacking to get it working, which may have been incomplete) maybe dracut needs to know about other possible paths for the file it is looking for.

Reproducible: Always

Steps to Reproduce:
1. Run any dnf5 update or install
2. Look at error output from scripts called by dnf and/or dracut
3.
Actual Results:  
Error after existing file is searched for apparently using the wrong path.

Expected Results:  
No errors.

Reverting rpm-ostree-2025.x to rpm-ostree-2024.9 removed other errors that may involve selinux despite the system not having selinux in enforcing mode. This is a new error for the specific configuration and kernel-6.12.11-200 in use.

Comment 1 Brian Morrison 2025-01-27 21:43:34 UTC
After a reinstall of all the kernel packages for 6.12.11 a further package shows a similar error:

>>> Running post-transaction scriptlet: kernel-uki-virt-0:6.12.11-200.fc41.x86_64
>>> Non-critical error in post-transaction scriptlet: kernel-uki-virt-0:6.12.11-200.fc41.x86_64
>>> Scriptlet output:
>>> /usr/lib/kernel/install.d/51-dracut-rescue.install: line 91: /boot/efi/loader/entries/a0d5bf658c974a57b308adf730de0c4c-0-rescue.conf: No such file
>>> /usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 1.
>>> 
>>> [RPM] %posttrans(kernel-uki-virt-6.12.11-200.fc41.x86_64) scriptlet failed, exit status 1

It would seem that the root cause may be similar or the same.

Comment 2 Brian Morrison 2025-01-29 21:00:13 UTC
Same with kernel-6.13.0-200

I can't work out where the /boot/efi/loader/entries directory comes from, unless something changed in recent kernel-core and kernel-uki-virt packages.

Comment 3 Brian Morrison 2025-01-30 22:02:36 UTC
Turns out that somehow selinux got set back into enforcing mode, which won't have helped.

I still don't understand exactly where this is failing, as far as I know /boot/efi/loader/entries has never existed.

Comment 4 Brian Morrison 2025-03-17 22:49:34 UTC
After a lot of searching and thinking, I finally realised that the presence of /boot/efi/<machine-id> caused the kernel updating scripts to think that grub2 was not in use and so none of the /usr/lib/kernel/install.d scripts were executing as expected for a grub2 controlled boot system.

sudo rm -rf /boot/efi/<machine-id> directory and reinstalling the current kernel-core package has returned everything to working again.

It wasn't dracut, so this bug report can be ignored and closed.


Note You need to log in before you can comment on or make changes to this bug.