Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696665 - [RFE] Check for unsupported syntax in custom ks files at upgrade time and suggest changes
Summary: [RFE] Check for unsupported syntax in custom ks files at upgrade time and sug...
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Provisioning Templates
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-05 11:38 UTC by Daniele
Modified: 2019-04-09 03:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Daniele 2019-04-05 11:38:49 UTC
Description of problem:
Sometimes the syntax for ks template files changes in new Satellite releases. For example:
Even though they might be documented in kb articles and release notes, most customers are not able to be on top of that. This means that, for those customers who have many custom templates, this is very disruptive. 
Since we already have tools to check the templates' syntax, it would be good to have such tools check the customer's templates and report required changes. Possibly, even propose automatic remediation.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create custom templates
2. Upgrade to a Satellite version that carries changes to the template files syntax
3. No warning is displayed at upgrade time
4. Provisioning fails

Actual results:
Provisioning fails if the syntax is not updated.

Expected results:
The installer to detect incompatible template files and notify the user, plus propose automatic remediation.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.