Bug 1228272 - When using systemd-boot, dracut uses wrong target file
Summary: When using systemd-boot, dracut uses wrong target file
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-24 10:07 UTC by Tilman Vogel
Modified: 2024-07-24 10:07 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tilman Vogel 2024-07-24 10:07:08 UTC 
When after an upgrade, 
  /usr/lib/module-init-tools/regenerate-initrd-posttrans 
runs 
  dracut -f --kver "$kver"
the generated initrd goes to
  /boot/efi/<somehexid>/$kver/initrd
which looks right but is in fact incorrect because
  /boot/efi/loader/entries/<somehexid>-$kver.conf
actually uses 
  initrd     /<somehexid>/$kver/initrd-$kver

Note the trailing "-$kver".

So, after running dracut, there are two initrds:
  /boot/efi/<somehexid>/$kver/initrd
  /boot/efi/<somehexid>/$kver/initrd-$kver
of which the former is the new one but ignored and the latter is an older one which will still be used.