Problem: We don't seem to be able to specify the timezone in the schedule #3577
Description
Issue
Problem: We don't seem to be able to specify the timezone in the schedule
We use Semaphore to schedule tasks on servers running in different timezone (Istanbul, London, Sydney, etc.).
This helps our devops process not to be impacted by various daylight saving hours happening at different time around the world.
To do that, we used the CRON_TZ feature in the schedule of the tasks. This has worked fine, with no errors, until version 2.10.32.
We recently upgraded to the latest version, and our schedules are showing this error:
We seem to be able to clock on save regardless. And the tasks trigger at the expected time. So, so far it doesn't look like the feature / crontab parsing stopped working.
Is this red message in error? (I.e.: not considering CRON_TZ as a valid parameter. ) Or is this feature being removed from the product?
Apologies if this was asked before, I couldn't find another ticket regarding CRON_TZ being set in the crontab line.
We did see this message below, but it seems to apply globally, and not at the schedule/task level:
Impact
Web-Frontend (what users interact with)
Installation method
Package
Database
Postgres
Browser
Firefox
Semaphore Version
2.16.51 (upgraded from 2.10.32)
Ansible Version
Logs & errors
No response
Manual installation - system information
No response
Configuration
No response
Additional information
No response