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.

Description of problem:

When scheduling a recurring job using the cronline option, it is not respecting the condition.

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

Satellite 6.8.4

How reproducible:

Schedule a recurring job using the cronline '30 22 1-7 * */3'.

Steps to Reproduce:
1. Schedule a recurring Job based on the cronline '30 22 1-7 * */3'.

Actual results:

" 30 22 1-7 * */3 " - It is running the job at 10:30 PM from 1st to 7th and on all Wed for every month.

Expected results:

" 30 22 1-7 * */3 " - It should run the job at 10:30 PM on the first Wed for every month.

Additional info:

I have tested this condition on the crontab (RHEL 7) and on the site https://crontab.guru/

Looking at parse-cron's source (the library we use for handling cronlines) it seems to make the assumption that "*/3" in the day of week place is equal to "0,3,6". That would roughly match the behaviour you're seeing.

There is a PR[1] opened against the upstream repository which should among other things fix this, but last movement there was in April 2016.

[1] - https://github.com/siebertm/parse-cron/pull/29

This is fixed by BZ1967030 . Maybe not exactly the way as described in #0, but it allows you to express things like "every first Wednesday in every month". I'll go ahead and close this as the other BZ described the same thing, but in slightly different words. If you feel the two BZs are different, feel free to reopen.