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.
+++ This bug was initially created as a clone of Bug #2220978 +++
Description of problem:
Provides day+1 of selected day when scheduling a recurring job through Monitor>Jobs page. Similar to 2036721
Legacy page works fine.
Version-Release number of selected component (if applicable):
6.13
How reproducible:
Always
Steps to Reproduce:
1. Schedule a recurring job from the Monitor>Jobs>Run Job page.
2. Select a day of the week.
3. Finalize the job and click run.
4. Verify date on the page that it brings you to.
Actual results:
Date is one day after selected day of the week
Expected results:
Date is the same as the day of the week selected
Additional info:
--- Additional comment from on 2023-07-18T08:37:02Z
I'm failing to reproduce this. If I now (2023-07-18, Tuesday) set the job to repeat weekly on Fridays, the job gets scheduled to be run on 2023-07-21 which is a Friday.
Any extra tips for reproducing this? What version of rubygem-foreman_remote_execution do you have?
--- Additional comment from on 2023-07-18T08:45:25Z
And on a maybe related note, what is your locale?
--- Additional comment from on 2023-07-19T18:12:13Z
I am currently showing rubygem-foreman_remote_execution-8.3.0-1.el8sat.noarch
Locale is EDT. I did try a variety of times to see if it was a time zone related issue.
--- Additional comment from on 2023-07-20T10:21:51Z
Still failing to reproduce it. Is the issue that the cron line gets generated incorrectly or that it gets generated correctly but then the times generated using it are off?
If you kick off a job to run on let's say Fridays, what do you see in the recurring logic tab in the job?
--- Additional comment from on 2023-07-20T19:22:22Z
After completing the wizard and selecting run, on the Overview tab it says the incorrect date. I selected Friday (7/21), at 12 noon (This should account for any timezone difference).
It displays "Scheduled to start at: 2023-07-22 12:00:00 -0400".
When selecting the Recurring logic tab it displays:
Cron line: 00 12 * * 6
Next Occurence: 2023-07-22 12:00:00 -0400
I would be happy to share screenshots or do a remote session/gmeet to help verify. I continued to duplicate this issue on my Satellite as I was writing the reply.
--- Additional comment from on 2023-07-28T10:05:28Z
Steps to reproduce:
1) Set your timezone to America/New_York for your browser. Setting it for your user inside Satellite seems to make no difference. Easiest way to achieve this is to start your browser like TZ=America/New_York firefox (feel free to substitute firefox for any browser you use)
2) Go to schedule a weekly recurring job
Actual results:
The days of week start with a Saturday, the started job is one day off
Expected results:
The days of week either start with a Sunday, but if they don't, it should be accounted for.
--- Additional comment from on 2023-07-28T10:43:50Z
Created redmine issue https://projects.theforeman.org/issues/36618 from this bug
--- Additional comment from on 2023-08-01T12:03:11Z
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36618 has been resolved.
--- Additional comment from on 2023-08-09T12:10:36Z
Verified on Satellite 6.14 sn 10
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 (Satellite 6.13.6 Async 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-2023:7461