Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2016-10-07 13:31:39 UTC
Description of problem:
When provisioning template is handedited, there can be multiple sources of errors.
1. safemode rendering issue - if the erb script being used is not approved for safemode rendering
2. referred snippet not found - If the snippet referred in the template is not found or misspelt
3. Any typos
But currently, there is no validation being done in the provisioning template. The user has to click on Preview manually to review the changes which is not that intuitive.
Version-Release number of selected component (if applicable):
satellite-6.2.2-1.1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. Go to Hosts -> Provisioning Templates -> hand edit any template with any typos or referring invalid snippet or adding a code which is not supported in safemode rendering.
2. Click submit
Actual results:
No error message shown to the user.
The user has to manually click on Preview of the Provisioning template to review the changes.
Expected results:
Whenever Provisioning Template is handedited, clicking on Submit should trigger automatic validation/preview of the template to make sure that there are no obvious errors. I know that we cannot capture 100% of the errors using this method, but the basic errors like typos, missed snippets, safemode methods can be captured which will save plenty of time while troubleshooting.
Additional info:
Template errors were vastly improved recently in 6.3, there is a new feature Template check, templates are verified when a host is entering build mode via "Review build status for xyz" modal dialog.
They are not checked when you edit them, that's not possible technically. There is a way to preview them, but error reporting will be the same (little bit unclear to the user).
I am closing this, we will unlikely be able to improve error reporting in preview mode, because the output is text/plain (it has to be it's 1:1 preview).