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.
DescriptionStephen Wadeley
2018-06-11 08:48:42 UTC
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/installation_guide/installing_satellite_server#synchronizing_time
Section Number and Name:
3.3.1. Synchronizing Time
Describe the issue:
chrony is the preferred NTP implementation in RHEL7, we need to change the section to present chrony as the default choice. The ntpd implementation should only be used when specifically required.
this line is not true (too simplistic, and conflates NTP with ntpd):
NTP is recommended for systems that are expected to remain in running states and are expected to be connected to a network without interruption.
Suggestions for improvement:
change this:
Two time synchronizers are available: NTP and chronyd. Each of these has its advantages. chronyd is recommended for systems that are frequently suspended and for systems, such as mobile and virtual systems, that intermittently disconnect and reestablish network connection. NTP is recommended for systems that are expected to remain in running states and are expected to be connected to a network without interruption.
To this:
Two NTP based time synchronizers are available: chronyd and ntpd. The chronyd implementation is specifically recommended for systems that are frequently suspended and for systems that have intermittent network access. The ntpd implementation should only be used when you specifically need support for a protocol or driver not yet supported by chronyd.
Then change this:
For more information on the differences between NTP and chronyd
to this:
For more information on the differences between ntpd and chronyd
Completely remove this procedure:
Synchronizing Time using NTP
In the few cases that a customer needs support for a hardware clock that only ntpd can provide, its quite likely that the clock is on another server dedicated to being an NTP server. So in the vast majority of cases Satellite uses can use chronyd and get its many advantages.
Additional information:
NTP is the protocol. The ntpd service is supplied by the ntp package. We do not need to mention that here, but it helps if you know that while writing or updating this section.