summaryrefslogtreecommitdiffstats
path: root/tools/docker-compose-minikube/minikube/tasks
diff options
context:
space:
mode:
authorSeth Foster <fosterseth@users.noreply.github.com>2024-12-11 17:14:58 +0100
committerGitHub <noreply@github.com>2024-12-11 17:14:58 +0100
commite605883592aa996ac65eceab3abc3106ab212e14 (patch)
tree451aec23de7905a8543bc646bb9fb6bed9303940 /tools/docker-compose-minikube/minikube/tasks
parentUse runtime log utility moved to DAB (#15675) (diff)
downloadawx-e605883592aa996ac65eceab3abc3106ab212e14.tar.xz
awx-e605883592aa996ac65eceab3abc3106ab212e14.zip
Do not fast forward rrule if count is set (#15696)HEADdevel
Fixes a bug where a schedule that was created to run only once will continue to run repeatedly. e.g. an rrule with dtstart 20240730; count 1; freq MINUTELY This job will run on 20240730, and should never run again. However, the next time the schedule update_computed_fields runs, the dtstart will fast forward to today's date, and next_run will be computed from that. This will trigger the job to run again, which is not intended. If count is set, we just should not fast forward the rrule and always calculate next_run based on original dtstart. Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Diffstat (limited to 'tools/docker-compose-minikube/minikube/tasks')
0 files changed, 0 insertions, 0 deletions