The RHEL84 custom boot does see/find/use the ks.cfg, as the %pre section runs successfully, and generates the partition table file in /tmp. This is the exact same code (for %pre, anyway) I've used in recent RHEL7.x ISO builds without problems. I've followed the Red Hat RHEL 8 docs for Anaconda, as well as for Kickstart, and Performing An Advanced RHEL Installation.
I am just blown away by how hard it is to simply fully
boot through to the end of the ks.cfg. I had none of these
issues/problems with RHEL5.x, 6.x and 7.x.
I've carefully looked over both repo lines in ks.cfg and verified the paths are correct.
I've provided the relevant lines from isolinux.cfg and grub.cfg (which are simple and straightforward).
Boots of either firmware present the same stubborn error state.
I've wondered if my building a RHEL84 ISO on a Centos7 VM could be the issue (how to know for sure?); not that it should matter though.
-Joe
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
