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.

Description of problem: In the current default provisioning templates there is a step to do an initial time sync using ntpdate:

```
#update local time
echo "updating system time"
/usr/sbin/ntpdate -sub <%= host_param('ntp-server') || '0.fedora.pool.ntp.org' %>
/usr/sbin/hwclock --systohc
```


In order for this to work the ntp package is also installed in the %packages system since is not install in rhel by default. 

From my understanding this line is just to do a quick initial sync. chronyd has an option to do this [1]. 

Most of our docs are (or are being updated to) prefer chrony [2]. 

So rather then install the ntp package to just use ntpdate once, we should probably consider using the 'chronyd -q' option. 

[1] https://chrony.tuxfamily.org/faq.html#_does_code_chronyd_code_have_an_ntpdate_mode
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1589712

Generally agree best to run the ntp update through a package provided by default rather than installing ntp.

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

Upstream bug assigned to stbenjam

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24290 has been resolved.

Verified fix in sat 6.6 snap 11

Provisioned a RHEL 8 box and it used chronyd to do an initial timesync.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3172