Description: Problem Statement

Customers often clone the default Kickstart template (e.g., Kickstart default) and introduce custom snippets or make modifications. When these custom snippets contain syntax or rendering issues, the host build request is successfully submitted, but the actual provisioning fails with a 500 Internal Server Error.

This misleads customers into believing the issue lies with networking or boot parameters, causing unnecessary troubleshooting and dissatisfaction.

*Exception Observed in client console:*

500 internal server error failed to fetch kickstart from https://satellite.example.com/unattended/provision?static=1&token=030c0635-8001-4a22-b2b2-dcf316eb868f

*From production logs:*

[E|app|3c65bda1] There was an error rendering the CSL_KS_ENG template:
[I|app|3c65bda1]   Rendering text template
[I|app|3c65bda1]   Rendered text template (Duration: 0.0ms | Allocations: 1)

*Expected Behavior:*

Satellite should validate all snippets used in the provisioning template during template preview or host build request, and block submission if a rendering error occurs.

*Impact:*

Hosts boot but fail during provisioning, breaking automation.

Misleading errors waste customer time and increase support overhead.

Customer dissatisfaction due to lack of proactive validation.

*Steps to Reproduce:*

Clone the default Kickstart default template.

Introduce a custom snippet (e.g., CSL_KS_ENG) that contains a rendering or syntax error.

Assign the template to a host group and initiate a host build.

Satellite accepts the build request.

Host fails provisioning with HTTP 500 error.

*Suggestion:*

Introduce a validation check that:

Recursively validates all included snippets during host build submission.

Shows clear template rendering errors in the Satellite UI before proceeding.