That was my feeling to. I hesitated a bit if I should file a bugzilla or not, as it did depend on what obviously is a non-standard directory on the hosts I saw it on. But with your encouragement I’ve now filed bug 1741340.
Given my previous discussion about the intention of the fields in the Boot Loader Specification, I’m not sure everyone will agree what is wrong here. It will be interesting to see.
The presence or absence appear a bit random. I checked two other F30 systems today, both of which have been upgraded several releases. One had what I first thought was a machine ID directory in /boot, but it turned out it was a different 32 digit hex sequence than the one in
/etc/machine-id. The other wasn’t converted to the BLS configuration method at all! It still had all boot entries directly in
grub.cfg. I’ve no idea why it looks that way.