"System BootOrder not found. Initializing defaults." Maybe a bug?

On a newly bought laptop HP Elitebook 850 G6 (without Windows but with FreeDos) I can boot

CentOS-8.1.1911-x86_64-dvd1.iso

from a USB stick just fine but when I try boot

fedora-coreos-32.20200601.3.0-live.x86_64.iso

this text is shown on the monitor

System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0009" with label "Fedora" for file "\EFI\fedora\shimx64.efi"

Reset System

and after about one second the computer is automatically rebooted.

When I enter the BIOS I can see that the setting: Configure Legacy Support and Secure Boot is set to Legacy Support Disable and Secure Boot Disable.

(That setting has not been changed since the computer came delivered)

It is possible to change that setting to either:
Legacy Support Enable and Secure Boot Disable
or
Legacy Support Disable and Secure Boot Enable

If I change to
Legacy Support Enable and Secure Boot Disable
a warning is shown that other settings in the BIOS need to be changed (for instance regarding Thunderbolt security) so I decided not to change that setting.

I restarted the computer and and pressed F9 to enter the Boot Menu.
Previously I had selected UEFI - Kingston DataTraveler 3.0 60A44 …
but this time I chose Boot from file which gave me the possibility to navigate in the file system down to the file shim64.efi
PciRoot(0x0)/Pci(0x14,0x0)/USB(0xC,0x0)/HD(1,MBR,0x6E2CF7 …

EFI

\fedora

\shimx64.efi\

Now Fedora CoreOS booted up just fine.

Is this a bug or expected behavior?
Thanks,
Erik Sjölund

You should maybe report that in the Fedora CoreOS tracker. Can you tell us how you wrote the ISO to your USB stick? Did you use the Fedora Media Writer?

I created a new issue
https://github.com/coreos/fedora-coreos-tracker/issues/563

Both USB sticks were written in this way:

sudo su -c "cat /tmp/fedora-coreos-32.20200601.3.0-live.x86_64.iso > /dev/sda"