[Spacewalk-list] Template variables not available

[Jon Miller]

Should I be able to use variables seen from a "cobbler system dumpvars"
command in my Spacewalk script? 

I am having a problem re-using a template enabled script from a cobbler
build system over on my Spacewalk server. The script is used to help setup
network interface configurations and starts with:
#if $getVar("system_name","") != ""

I do not have "system_name" defined in my System Details -> Variables section
on Spacewalk but I do see the variables via the "cobbler system dumpvars
--name=server-16":
...
system_name : server-16
...

That #if block always fails and I'm not getting my interfaces configured at
all. If I ask for the kickstart file via cobbler (on my Spacewalk server), it
yields the block correct:
sudo cobbler system getks --name=server-16

Perhaps my problem is how I'm initiating the kickstart? I'm using a corporate
PXE server that I can update and have created an entry that uses the
following boot options:
  ks=http://spacewalk.example.com/ks/cfg/org/6/label/test-profile
  initrd=fedora18-x86_64/initrd.img text nofb noipv6 network kssendmac 

I thought I just needed to have kssendmac included and Spacewalk would see
the server... Actually, while composing this, I noticed that the dumpvars
command has "mac_address_eth0 : 00:15:17:9b:6a:d0" and this is a Fedora 18
build and I'm guessing it had interface em1 UP and not an eth0. Could that
explain why Spacewalk isn't identifying my machine and pulling in the cobbler
variables? I'm going to test with adding "biosdevname=0" to my kernel boot
options.

-- 
Jon Miller