-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timezone for CronWorkflow not working for all expected zones #5653
Comments
Will take a look |
@endzyme can you please confirm if this worked in v2.12? |
It did, but I'll try to spin something up this coming week to provide proof. I saw your note on the related Dockerfile change. It's likely related but I haven't fully dug into why some timezones would work and others would not. |
|
|
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Apr 19, 2021
Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec
added a commit
that referenced
this issue
Apr 19, 2021
simster7
pushed a commit
that referenced
this issue
Apr 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Timezone settings for CronWorkflows don't appear to work for all expected timezones. I have set a timezone of
Europe/Dublin
and the controller does not actually start the job. There are some log messages that it is processing the job but nothing appears to start. When I changed toAmerica/New_York
orEurope/Paris
it appears to work. I have also tested withEtc/GMT-1
andEurope/Amsterdam
and same results, no worky.Diagnostics
What version of Argo Workflows are you running?
v3.0.1
I will provide logs if needed.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: