Bug #21263
closed
Time zone changes in Schedule future execution & Set up recurring execution
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1426568
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:
Updated by Adam Ruzicka over 6 years ago
- Target version set to 113
Using scheduled run uses the user's timezone, recurring logic takes the server's timezone. We should take into account the user's timezone when creating recurring logics.
Updated by Ivan Necas about 6 years ago
- Has duplicate Bug #14378: Wrong timezone in start_at field added
Updated by Anonymous about 6 years ago
- Related to Bug #15091: Wrong timestamps on failed tasks if user uses different timezone settings added
Updated by Anonymous about 6 years ago
I cannot replicate the problem(s) described in this ticket: both scheduled tasks and future executions respect browser's timezone. It appears that https://github.com/theforeman/foreman-tasks/commit/fabd05cb15fc6757c4d9d8b0666c651c0ebb68aa fixed time-zone issues.
Updated by Ivan Necas about 6 years ago
Interesting, it seemed I was able to reproduce this recently, but when trying with https://github.com/theforeman/foreman-tasks/pull/311/files, the behaviour seemed consistent.