Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 2026301

Summary: Cannot remediate Configure Time Service Maxpoll Interval
Product: Red Hat Enterprise Linux 8 Reporter: Ales Musil <amusil>
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Milan Lysonek <mlysonek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: ggasparb, mhaicman, mlysonek, mperina, wsato
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.60-3.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 14:15:29 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:
Bug Depends On:    
Bug Blocks: 2015802    

Description Ales Musil 2021-11-24 10:26:27 UTC
Description of problem:
Automatic remediation of rule "Configure Time Service Maxpoll Interval" does 
not work. 

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


How reproducible:
100%

Steps to Reproduce:
1. oscap xccdf eval --remediate  --profile xccdf_org.ssgproject.content_profile_stig --rule xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml


Actual results:
Title   Configure Time Service Maxpoll Interval
Rule    xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll
Ident   CCE-84059-5
Result  fail


 --- Starting Remediation ---
WARNING: Skipping ./security-data-oval-com.redhat.rhsa-RHEL8.xml file which is referenced from XCCDF content
Title   Configure Time Service Maxpoll Interval
Rule    xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll
Ident   CCE-84059-5
Result  error


Expected results:
The remediation should pass

Additional info:
Content of chrony.conf:
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
pool 2.rhel.pool.ntp.org iburst

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

# Allow the system clock to be stepped in the first three updates
# if its offset is larger than 1 second.
makestep 1.0 3

# Enable kernel synchronization of the real-time clock (RTC).
rtcsync

# Enable hardware timestamping on all interfaces that support it.
#hwtimestamp *

# Increase the minimum number of selectable sources required to adjust
# the system clock.
#minsources 2

# Allow NTP client access from local network.
#allow 192.168.0.0/16

# Serve time even if not synchronized to a time source.
#local stratum 10

# Specify file containing keys for NTP authentication.
keyfile /etc/chrony.keys

# Get TAI-UTC offset and leap seconds from the system tz database.
leapsectz right/UTC

# Specify directory for log files.
logdir /var/log/chrony

# Select which information is logged.
#log measurements statistics tracking

# Per CCE-82988-7: Set port 0 in /etc/chrony.conf
port 0

# Per CCE-82840-0: Set cmdport 0 in /etc/chrony.conf
cmdport 0

Comment 2 Watson Yuuma Sato 2021-11-24 11:40:10 UTC
Proposed PR: https://github.com/ComplianceAsCode/content/pull/7910

Comment 11 Watson Yuuma Sato 2022-02-11 15:26:06 UTC
Propose fix: https://github.com/ComplianceAsCode/content/pull/8187

Comment 21 errata-xmlrpc 2022-05-10 14:15:29 UTC
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 (scap-security-guide bug fix and enhancement update), 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-2022:1900