Foreman 1.7.0 default kickstart scripts broken, http error 500

Hello,

I have a fresh installation of Foreman 1.7.0 on CentOS 6.6, and I'm seeing a problem with the default kickstart scripts.
Basicly I'm unable to install any hosts, because the kickstart file cannot be fetched from foreman server, it gives http 500 error.

https://<foreman-server-name>/unattended/provision?hostname=<new-host-hostname>

gives HTTP 500 Internal Server Error:
"There was an error rendering the Kickstart default template: The snippet 'kickstart_networking_setup' threw an error: private method `layout' called for nil:NilClass"

I haven't edited any of the provisioning templates myself, these are the defaults out-of-the-box.
Also I can't edit the kickstart script for any new host from the foreman webUI because I get that same error.

So… any idea what actually is the problem in those kickstart scripts? I tried reading the scripts,
but I don't see anything obvious… I guess I need to dig in deeper.

Thanks,

– Pasi

Hmm… I guess this is caused by staypuft, which seems to modify the default kickstart.

Maybe I should post to the dev list…

– Pasi

··· On Thu, Dec 11, 2014 at 02:51:08PM +0200, Pasi Kärkkäinen wrote: > Hello, > > I have a fresh installation of Foreman 1.7.0 on CentOS 6.6, and I'm seeing a problem with the default kickstart scripts. > Basicly I'm unable to install any hosts, because the kickstart file cannot be fetched from foreman server, it gives http 500 error. > > https:///unattended/provision?hostname= > > gives HTTP 500 Internal Server Error: > "There was an error rendering the Kickstart default template: The snippet 'kickstart_networking_setup' threw an error: private method `layout' called for nil:NilClass" > > > I haven't edited any of the provisioning templates myself, these are the defaults out-of-the-box. > Also I can't edit the kickstart script for any new host from the foreman webUI because I get that same error. > > So.. any idea what actually is the problem in those kickstart scripts? I tried reading the scripts, > but I don't see anything obvious.. I guess I need to dig in deeper. >