I'm not totally sure if the workaround in the issue was the solution, because the error is related directly with dnf parameters customizable on the settings.yaml, but anyway, is this: cobbler/cobbler#2519
Newbie question... I looked through the docs but I am coming up short: When I add certain packages to the %packages section of the kickstart the install stops at the above screenshot ^ So where are these supposed to live?
So I found some of the packages in a iso called gs-184.108.40.206-RHEL-r84-x86_64 under the/var/www/cobbler/ks_mirror directory. From what I am reading , I should add the path to the ISO so that the kickstart can look in the Packages dir and grab the rpm's... eh?
Yes but how do we generate that links? Since currently Cobbler knows the paths to the Kernel & Initrd I think just serving that file would be best instead of putting additonal logic into accepting more path possibilities. Also then it is under Cobbler control and we don't need to support addtional setups. I mean I can understand your reasoning but so far I don't see the "big" advantage in it compared to mine.
UEFI HTTP booting (pure http, not the kind that uses ipxe chainloading) requires updates to the dhcp.conf file in order for the httpboot client to find the boot files from a web URL. In my former job, i had to hack my way through figure most of it out. It would be nice if official directions can be given (or maybe the dhcp.template file could include a section for http booting by default). Unfortunately, i didnt finish the implementation and am no longer in that role. It would be nice for my replacement to have a good doc though. Thoughts?