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.

Bug 2036721

Summary:	Satellite is creating the schedule on the wrong day of the week (day+1)
Product:	Red Hat Satellite	Reporter:	alsanche
Component:	SCAP Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	mhulan, pcreech, rlavi
Target Milestone:	6.11.0	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_openscap-5.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:31:28 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:

Description alsanche 2022-01-03 17:17:42 UTC

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

Comment 1 Brad Buckingham 2022-01-05 15:16:50 UTC

Moving to ASSIGNED as there is a PR upstream.  The redmine associated with that PR is now also attached.

Comment 2 Ron Lavi 2022-02-01 13:21:40 UTC

upstream PR is merged and released in foreman_openscap.1 gem

Comment 3 Ron Lavi 2022-02-07 13:46:03 UTC

created tfm-rubygem-foreman_openscap-5.1.1, hopefully it will make it to one of the upcoming snaps

Comment 4 Jameer Pathan 2022-04-06 13:16:12 UTC

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

Comment 7 errata-xmlrpc 2022-07-05 14:31:28 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 (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