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 1646525 - Recurring Logic / Recurring Execution Monthly Ignores "Day" field
Summary: Recurring Logic / Recurring Execution Monthly Ignores "Day" field
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.3.4
Hardware: All
OS: Linux
unspecified
low
Target Milestone: 6.6.0
Assignee: Adam Ruzicka
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 16:00 UTC by Samson Wick
Modified: 2022-03-13 15:58 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-0.14.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:47:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25395 0 Normal Closed Recurring Logic / Recurring Execution Monthly Ignores "Day" field 2020-11-02 04:15:00 UTC

Description Samson Wick 2018-11-05 16:00:10 UTC 
Description of problem: When configuring a Job to recur and selecting "Monthly" as the frequency, the current day of the month is always used regardless of what value(s) is placed in the "Day" field.


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


How reproducible: 


Steps to Reproduce:
1. From the Satellite GUI, browse to Monitor->Jobs
2. Click "Run Job"
3. Select any value for Category, Template, Search Query.
4. Provide any value for "command".
5. Check the bullet for "Set up recurring execution"
6. Select "Monthly" for "Repeats"
7. In the "Days" field, provide any day or combination of days other than the current day of the month.
8. Click "Submit"
9. Observe that the next occurrence is scheduled on the same day as the present day next month, irrespective of what day of the month was specified.

Actual results:
The recurring task is scheduled for the same day of the month as the present day, not the day specified.  For example, if the recurring logic is created on 11/5, execution will be scheduled to always occur on the 5th of each month regardless of what date was specified.


Expected results:
The recurring task is scheduled for the day or days of the month specified on the form.


Additional info:
This has been tested with Satellite 6.3.4 and 6.4, using the latest versions of Firefox and Chrome, running on both Linux and Windows.

As a workaround, "cronline" can be used to produce the desired result.
Comment 1 Adam Ruzicka 2018-11-06 11:44:05 UTC 
Created redmine issue http://projects.theforeman.org/issues/25395 from this bug
Comment 3 Satellite Program 2018-12-06 21:02:40 UTC 
Upstream bug assigned to aruzicka
Comment 4 Satellite Program 2018-12-06 21:02:43 UTC 
Upstream bug assigned to aruzicka
Comment 5 Satellite Program 2018-12-07 17:02:06 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25395 has been resolved.
Comment 8 Bryan Kearney 2019-10-22 19:47:46 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, 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.