Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1786182

1. Proposed title of this feature request

Improve handling of template rendering failures and reporting of errors.

3. What is the nature and description of the request?

When a template fails to render, it returns a vague error in the UI saying:

"We're sorry, but something went wrong.
       If you are the application owner check the logs for more information."

This does not give the impression that it's necessarily a template rendering error (as the page is devoid of any of the Satellite UI components, but appears to be just a 500 Internal Server Error).   This suggests to the user there could be larger internal satellite issues at hand.

4. Why does the customer need this? (List the business requirements here)

Satellite users who have ability to manage hosts and templates do not always have access to the Satellite's system's logs.   If the UI user is told that the problem is a template rendering error (and perhaps where the error occurs) it would simplify troubleshooting

5. How would the customer like to achieve this? (List the functional requirements here)

Ideally the error could be caught and displayed within the Satellite WebUI so that the user doesn't think it's just some httpd or other issue.   Also, if the nature of the error and a line number of where the error occurred in the template, that would be useful

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Cause a template to fail to render.  Be able to discern from the error in the WebUI that it is a template rendering error, and what part of the template had the issue.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

No.

(While Bug 1776515 - "[RFE] Improve Reporting and Kickstarts Templates editing" initially seemed similar from the title, it was asking for was the creation of a form or tool to abstract the creation of templates. )

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No

9. Is the sales team involved in this request and do they have any additional input?

No.

10. List any affected packages or components.

Red Hat Satellite 6.6

11. Would the customer be able to assist in testing this functionality if implemented?

Yes.