RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Installation with DISA STIG security profile includes a misconfigured /etc/chrony.conf file which does not allow the chronyd service to start. 


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


How reproducible: 100%


Steps to Reproduce:
(1) Install from installation media
-minimal load
-set network and hostname
-default partitioning
-DISA STIG security profile
(2) Set root password and create administrative user during installation (STIG profile will not allow root login at console)
(3) Reboot after installation
(4) Log in as administrative user, execute sudo -s
(5) Run "systemctl start chronyd" and review output
(6) Run "systemctl status chronyd" and review output

Actual results:
chronyd service fails to start

Expected results:
chronyd service starts


Additional info:
(1) Problem does not exist in installation with no security profile selected.
(2)Manually changing the "iburst1" parameter to "iburst" for the server entries in /etc/chrony.conf allows the service to start normally.

It looks like this issue:

https://github.com/OpenSCAP/scap-security-guide/issues/2551

Reassigning to openscap.

Reassigning to SSG.

Indeed.
patch: https://github.com/OpenSCAP/scap-security-guide/pull/2552

Verified manually on version scap-security-guide-0.1.40-5.el7

`/etc/chronyd.conf` after reboot contains these lines, and chronyd starts:

[root@localhost ~]# grep maxpoll -C3 /etc/chrony.conf 
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server 0.rhel.pool.ntp.org iburst maxpoll 10
server 1.rhel.pool.ntp.org iburst maxpoll 10
server 2.rhel.pool.ntp.org iburst maxpoll 10
server 3.rhel.pool.ntp.org iburst maxpoll 10

# Record the rate at which the system clock gains/losses time.
driftfile /var/lib/chrony/drift

[root@localhost ~]# systemctl status chronyd
● chronyd.service - NTP client/server
   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-09-17 01:03:31 CEST; 5min ago

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/RHBA-2018:3308