Bug 2243263

Summary: dtb files no longer copied into /boot
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 39CC: awilliam, fedoraproject, filbranden, lnykryn, msekleta, robatino, ryncsn, systemd-maint, yuwatana, zbyszek
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-11 18:23:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2143446    

Description Dennis Gilmore 2023-10-11 13:44:55 UTC 
after updating to systemd-udev-254.5-2.fc39.aarch64 the dtb files on a new kernel install are not copied into /boot 

lrwxrwxrwx.  1 root root       26 Oct  9 08:21 dtb -> dtb-6.5.6-300.fc39.aarch64
drwxr-xr-x. 18 root root     4096 Sep 25 13:25 dtb-6.5.4-300.fc39.aarch64
drwxr-xr-x. 18 root root     4096 Sep 26 11:32 dtb-6.5.5-300.fc39.aarch64


Is the contents in /boot dtb is a broken symlink. I have had this happen on two systems. For some systems, such as my espressobins the result is a system that no longer boots because the dtb file can not be found.

Reproducible: Always
Comment 1 Dennis Gilmore 2023-10-11 15:27:45 UTC 
possibly it is due to https://github.com/systemd/systemd/commit/2bca841137833edeaf3779542d6475f0dc3aa5a7 not being in our build
Comment 2 Adam Williamson 2023-10-11 16:59:36 UTC 
This looks like https://bugzilla.redhat.com/show_bug.cgi?id=2243060 ?
Comment 3 Dennis Gilmore 2023-10-11 18:16:12 UTC 
likely, I updated a couple of other systems and they are not seeing the issue
Comment 4 Adam Williamson 2023-10-11 18:23:00 UTC 
okay, let's call it a dupe...you can try updating the affected system to grub2 -104, I guess...

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