Comment 1 for bug 1906379

I'm not sure if the entry is deleted, or indeed, fails to be added.

I'm deploying onto nvme drive and whilst:

chroot /mnt efibootmgr -v --create --write-signature --label centos --disk /dev/nvme0n1 --part 1 --loader /boot/efi/EFI/centos/shimx64.efiCould not prepare Boot variable: No such file or directory

fails, (aka using efibootmgr from the chrooted system) whilst booted into ubuntu's v5.4 kernel.

But running the same command from focal environment (i.e. without chroot). Does succeed fine:

efibootmgr -v --create --write-signature --label centos --disk /dev/nvme0n1 --part 1 --loader /boot/efi/EFI/centos/shimx64.efi

$ sudo efibootmgr -v --create --write-signature --label centos --disk /dev/nvme0n1 --part 1 --loader /boot/efi/EFI/centos/shimx64.efi
BootNext: 0002
BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0000,0002,0003,0004,0005,0006,0001
Boot0001* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0002* UEFI: PXE IP4 Intel(R) I350 Gigabit Network Connection PciRoot(0x3)/Pci(0x3,0x4)/Pci(0x0,0x0)/MAC(18c04d711026,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0003* UEFI: PXE IP4 Intel(R) I350 Gigabit Network Connection PciRoot(0x3)/Pci(0x3,0x4)/Pci(0x0,0x1)/MAC(18c04d711027,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0004* UEFI: PXE IP6 Intel(R) I350 Gigabit Network Connection PciRoot(0x3)/Pci(0x3,0x4)/Pci(0x0,0x0)/MAC(18c04d711026,1)/IPv6([::]:<->[::]:,0,0)..BO
Boot0005* UEFI: PXE IP6 Intel(R) I350 Gigabit Network Connection PciRoot(0x3)/Pci(0x3,0x4)/Pci(0x0,0x1)/MAC(18c04d711027,1)/IPv6([::]:<->[::]:,0,0)..BO
Boot0006* UEFI OS HD(1,GPT,86ad9d07-0596-4077-965b-bded3e4da2e5,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0000* centos HD(1,GPT,86ad9d07-0596-4077-965b-bded3e4da2e5,0x800,0x100000)/File(\boot\efi\EFI\centos\shimx64.efi)

I wonder if there rhel 8 efibootmgr is compatible with v5.4 ubuntu kernel, w.r.t. nvme drives.