Description of problem: The selected day of the week was Wednesday and not Thursday The correct schedule in crontab should be 0 1 * * 3 root /bin/sleep 203; /usr/bin/foreman_scap_client 2 2>&1 | logger -t foreman_scap_client instead of 0 1 * * 4 root /bin/sleep 203; /usr/bin/foreman_scap_client 2 2>&1 | logger -t foreman_scap_client Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Hosts > Compliance > Policies 2. Click on schedule 3. Schedule the policy Actual results: Does not run on scheduled day, but a day later Expected results: It should run on the scheduled day Additional info: The customer has actually solved this upstream: https://github.com/theforeman/foreman_openscap/pull/521
Moving to ASSIGNED as there is a PR upstream. The redmine associated with that PR is now also attached.
upstream PR is merged and released in foreman_openscap.1 gem
created tfm-rubygem-foreman_openscap-5.1.1, hopefully it will make it to one of the upcoming snaps
Verified: Verified with: - Satellite 6.11 snap 15 - rubygem-foreman_openscap-5.1.1-1.el8sat.noarch Test steps: - Create compliance policy scheduled to run on Wednesday every week. - Assign it to host. - Configure Openscap for the host. Observation: - /etc/cron.d/foreman_scap_client_cron had correct schedule. (Refer https://api.rubyonrails.org/v6.1.4/classes/DateAndTime/Calculations.html) # foreman_scap_client cron job 0 1 * * 3 root /bin/sleep 185; /usr/bin/foreman_scap_client ds 1 2>&1 | logger -t foreman_scap_client
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 (Moderate: Satellite 6.11 Release), 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-2022:5498