Project

General

Profile

Actions

Bug #14378

closed

Wrong timezone in start_at field

Added by Marek Hulán about 8 years ago. Updated over 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When tasks gets created but is not run yet, you can see that start_at is set without respecting the timezone. On my system it was shifted by 2 hours from started_at. Once executor runs the task, time gets updated correctly. Tested with 0.7.15


Related issues 2 (1 open1 closed)

Related to foreman-tasks - Bug #14377: All tasks are displayed with execution type delayedNew03/29/2016Actions
Is duplicate of foreman-tasks - Bug #21263: Time zone changes in Schedule future execution & Set up recurring executionResolved10/10/2017Actions
Actions #1

Updated by Marek Hulán about 8 years ago

  • Related to Bug #14377: All tasks are displayed with execution type delayed added
Actions #2

Updated by Ivan Necas over 6 years ago

  • Is duplicate of Bug #21263: Time zone changes in Schedule future execution & Set up recurring execution added
Actions #3

Updated by Ivan Necas over 6 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF