I have been working with AlmaLinux 8 for a couple of years using various iterations AlmaLinux 8, with my systems(5 of them) currently using 8.10. I am now in the process of validating install media to move to version 9.4, using kickstart to manage the initial configuration of these hosts. The kickstart file sets up the network,decides the host name, and sets up a complex partitioning scenario. Initially I tested this using secure boot, without any issue. I repeated the same install, on the same hardware, using the same kickstart file, only this time using the legacy boot (insecure). I have verified that this is an issue with insecure boot, as I then did a manual install of a server+graphics, along with development tools, and then took the resulting kickstart file, made the required changes so that the partitioning would work, and then attempted to do a kickstart install using this minimal kickstart, with the same results of success for the EFI boot, and failure with the isolinux boot. I did check, and the two commands to the kernel appear to be identical, but the insecure boot is not able to find the kickstart file. Has anyone else seen this behavior? Anyone found a work-around?
