Add job and start deadlines to the g10k-code CronJob #490
Reference in New Issue
Block a user
Delete Branch "benvin/g10k-hung-job-deadline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A g10k-code job wedged in ContainerCreating on a failed CephFS mount and never reached a terminal condition, so it stayed in the CronJob active list and
concurrencyPolicy: Forbidskipped every following minute. No Puppet code reached the estate for 6 days, and the piled-up missed slots crossed the controller 100-slot cap intoTooManyMissedTimes. The CronJob carried no deadlines at all.activeDeadlineSeconds: 300on the Job spec, so a hang is failed asDeadlineExceededand drops out of the active list (healthy runs take 16-18s).startingDeadlineSeconds: 200, bounding missed-schedule look-back to ~3 slots so the count cannot reach 100.