Admittedly I am a far cry from a knowledgeable foreman provisioner, but
with the assistance of others I mostly muddle along… but I need help.
I am running foreman/katello from git and have set up a network named
"provisioning" for my katello install. I'm running libvirt compute resource.
At the moment, I get an error of "Could not find kernel image: linux" at
the start of provisioning. After poking around the templates, I see that
word in the "Kickstart default PXELinux" template, "DEFAULT linux". At this
point I'm dropped to the boot: prompt. Some googling later (and lots of
failures) I entered "kickstart_cmdline" at that prompt. Magic! The install
finished and the VM rebooted… and back to the boot: prompt with same
error message.
And now I'm just stuck in a loop if I enter kickstart_cmdline again. It
just reinstalls everything and reboots, landing me back at the boot: prompt.
I'm sure this is user error but I'm not sure where or what to look for.
> And now I'm just stuck in a loop if I enter kickstart_cmdline again. It
> just reinstalls everything and reboots, landing me back at the boot: prompt.
>
> I'm sure this is user error but I'm not sure where or what to look for.
It is, but its not your fault
You happened to clone/update git in a short few days window when there
was a typo, DEFAULT linux is incorrect, it should read something else
(the first LABEL entry).
Synchronization of Foreman templates from community-templates in
713be41b fixes it, but git merge won't help you - you need to delete the
Kickstart PXELinux template and re-seed your database in order to have
it recreated.
As an alternative, you can use foreman templates plugin to reseed your
templates:
Make sure you give it an empty prefix, otherwise you will end up with
zillions of copies prefixed with "Community" and your old one will be
unchanged.
Beware, this will overwrite all your templates to match our upstream!
Seeding is perhaps safer for you, but this is a good exercise, because
people tend to upgrade Foreman from git or RPM but templates are usually
unchanged for years and then we have reports that something does not
work (because of very outdated template).
