On 26.10.2015 [12:15:00 -0700], Zarko Dudic wrote:
The kickstart file is specific for the system, added via web
interface Systems - General - Kickstart and it's verified by
selecting Systems - View Kickstart.
Ok, so you generally either want system-specific kickstarts or let the
system inherit it from the profile you assign to a system (e.g., to
install that system with that profile (OS)) -- at least, in my
understanding.
Fair enough that Cobbler updates files in /var/lib/tftboot on sync,
but why any kickstart info is missing?
What OS are you using? Did you use `cobbler import` to add it? Not every
OS needs ks=. I thought I was being pretty clear when I asked for more
details, but please indicate your full use-case from start to end.
In general, users I support reinstall the OS all the time, so
it's
crucial for them to use kickstart with specified network parameters,
all I need to do on DHCP is to have the next-server pointing to
Cobbler.
Ok? I'm not sure what this has to do with the issue, but thank you for
clarifying your use-case.
As of kickstart associated to the profile, it's again done via
web
interface Profiles - Edit - General - Kickstart.
And once server pxe-boot and hits Cobbler and profile is selected,
the installation fails since the kickstart info is missing.
It would be great if some has has done similar exercise or have some
best practices in mind.
To know what "similar exercises" are, or "best practices" would be,
you
*must* provide some actual information. So far, your messages have been
fairly vague.
-Nish