Description of problem:

Bootdisks generated by Satellite don't include the file mmx64.efi. Under certain circumstances, this may be needed to boot the system to be provisioned.

UPDATE: trying to better explain the certain circumstances so that this might be correctly prioritized here.
What seems to be happening is that certain HW (for instance HPE Superdome Compute Scale-up Server 3200) has a pending request to load the mokutil and so it's trying to do it when the system boots: it's there and the firmware is trying to honor it.

As the bootdisk from Satellite does not include this file, it errors out.

Also confirmed by anaconda engineering: what happens is that the uefi bios/firmware has a pending request to load the mmx64.efi (to load certificates most likely) and regardless of secureboot being enabled; thus the request must be pending at the bios which tries to load it.

Is this issue a regression from an earlier version:

 no

Actual behavior:
bootdisk does not include mmx64.efi inside the efiboot.img

Expected behavior:
would like efiboot.img to include mmx64.efi. Currently it only contains these files:

./EFI
./EFI/BOOT
./EFI/BOOT/GRUB.CFG
./EFI/BOOT/GRUBX64.EFI
./EFI/BOOT/BOOTX64.EFI

Business Impact / Additional info:

QE Tracker for https://issues.redhat.com/browse/SAT-38396