I discovered a problem with our cobbler server this morning and am
having a hard time tracking down the root cause. I would like to know
if/how I could get more debugging output from the "cobbler sync" command.
We use a single kickstart cheetah template for all of our profiles and
source in the correct parition scheme for a system based on some
hardware configs that are part of our ksmeta data.
## PARTITIONING:
#if $getVar("hardware","none") == "none"
## Default:
SNIPPET::partition_select
#else if $getVar("hardware", "None") == "8832sem"
SNIPPET::PART.8832sem
#else if $getVar("hardware", "None") == "8832"
SNIPPET::PART.8832
#else if $getVar("hardware", "None") == "8843sem"
SNIPPET::PART.8843sem
#else if $getVar("hardware", "None") == "8843"
SNIPPET::PART.8843
#else if $getVar("hardware", "None") == "8853sem"
SNIPPET::PART.8853sem
In the case of the 8843sem and 8853sem, the letters "sem" are inserted
into the ks.cfg right after the contents of the PART.8853sem snippet
file. This isn't the case for the 8832sem.
Also, I've quadruple checked the contents of the PART.8853sem and
PART.8843sem files and "sem" isn't hidden anywhere, so I'm sure its
happening in the logic above.
If I make a symlink named "PART.8853semSL" and point it back to the
8853sem file, everything works.
We are using cobbler-0.8.2-1 at this time, so I hope we aren't so out of
date that everyone has forgotten how cobbler used to work! ;)
Any help or tips are appreciated.
Thanks,
Tom
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
