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.
DescriptionPradeep Kumar Surisetty
2017-02-24 10:51:58 UTC
Description of problem:
Remote execution can be run 3 ways
1) Execute now
It executes after submitting job (No time zone issues)
2) Schedule future execution
It considers time zone from where you are running.
In my case IST
3) Set up recurring execution
It considers time zone where your lab where satellite running.
in my case EST
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. try Set up recurring execution & Schedule future execution
from different time zones.
2.
3.
Actual results:
Expected results:
Additional info:
Checked on
foreman-1.18.0-0.develop.201804061848git210e295.el7.noarch
tfm-rubygem-foreman-tasks-0.13.0-1.fm1_18.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.4-1.fm1_18.el7.noarch
Recurring execution adheres to the user timezone settings
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-2018:2927
Hello,
One of our customers has reported that they are facing this issue on Satellite 6.4.2. I have reproduced the issue and it looks to be valid.
>> I created recurring job to be executed 04:15 AM IST everyday. Timezone set at my browser is IST.
~~~
Cron line 15 04 * * *
~~~
- The first job executed successfully at 04:15 AM IST.
- The next scheduled job was showing and executed at 09:45 AM IST (04:15 UTC). See screenshot rex_task_1.png.
- And all the next tasks are scheduled to execute at 09:45 AM IST (04:15 UTC) See screnshot rex_task_2.png.
Let me know if this is regression or new a new Bugzilla this.
Regards,
Rajan