Daylight Savings time requires manual intervention for tasks to start executing again if the Trigger start time is close to when the timezone changes

[danefalvo]

Team

• [X] I've assigned a team label to this issue

Severity

Temporarily blocked one customer

Version

2022.4.4601 (hotfix: 5911)

Latest Version

I could not reproduce the problem

What happened?

When the timezone changed from IST (+2) to IDT (+1) a single job that was scheduled to trigger, ended up queuing but not executing blocking all new jobs in the Octopus Task Queue.

https://octopus.zendesk.com/agent/tickets/99734 Story Created here: https://app.shortcut.com/octopusdeploy/story/29977

Unlike this issue, the customer has noted that all of the deployments were still queued 7 hours later and required cancelling.

Reproduction

I have set up an environment where there is an internally controlled NTP, thus simulating a proper Daylight savings change by simulating the exact moment the Time changes. Unfortunately, I am unable to reproduce the issue.

Although logging gets confused, (A tasks finish time, may be before it's start time or messages like "This task started 3 minutes from now") there are no unexpected issues with deployments and deployment triggers and no tasks stuck in the queue.

Error and Stacktrace

No response

More Information

No response

Workaround

Cancel all of the queued tasks.