Bug 2240961

Summary:	kickstart_kernel_options deprecation warning - ks param on rhel8
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Provisioning Templates	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Shweta Singh <shwsingh>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.14.0	CC:	gisoni, lstejska, mhulan, rlavi, shwsingh
Target Milestone:	Unspecified	Keywords:	EasyFix, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:30:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roman Plevka 2023-09-27 11:05:44 UTC

Description of problem:
when provisioning RHEL8 using kickstart, there is a deprecation warning displayed regarding 'ks' paramter.
this has been taken care of for RHEL9,
https://github.com/theforeman/foreman/blob/develop/app/views/unattended/provisioning_templates/snippet/kickstart_kernel_options.erb#L40-L56

However, we could include RHEL8 in the conditional too to prevent the warning from being displayed.

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


Steps to Reproduce:
try to kickstart provision a RHEL8 host (make sure the `kickstart_kernel_options` template is used)

Actual results:
Warning just after the anaconda installer is initialized

Expected results:
no deprecation warnings

Additional info:

Comment 1 Girija Soni 2024-04-11 09:00:08 UTC

Created redmine issue https://projects.theforeman.org/issues/37343 from this bug

Comment 2 Eric Helms 2024-06-06 16:30:16 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.