Bug 2237415

Summary:	Using use-ntp host parameter installs ntpdate which is no longer available in RHEL8+
Product:	Red Hat Satellite	Reporter:	Gaurav Talreja <gtalreja>
Component:	Provisioning Templates	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Shweta Singh <shwsingh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	lstejska, mhulan, rlavi, sganar, shwsingh
Target Milestone:	6.15.0	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
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:28:56 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 Gaurav Talreja 2023-09-05 12:05:39 UTC

Description of problem:
https://github.com/theforeman/foreman/blob/develop/app/views/unattended/provisioning_templates/snippet/ntp.erb#L21

Version-Release number of selected component (if applicable):
Satellite 6.14/6.13

How reproducible:
Always

Steps to Reproduce:
1. Try to provision a host with use-ntp param

Actual results:
use-ntp will install ntpdate package which isn't available

Expected results:
use-ntp should use chrony suite to configure ntp,


Additional info:
https://access.redhat.com/solutions/4130881

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/using-chrony-to-configure-ntp_configuring-basic-system-settings#doc-wrapper

Comment 1 Leos Stejskal 2024-05-16 11:33:50 UTC

Moving to ON_QA, this has been resolved for a while.
See https://github.com/theforeman/foreman/pull/9544

Comment 2 Eric Helms 2024-06-06 16:28:56 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.