Add a way to suspend CronJobs
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Clement_Goubert
	May 15 2025, 1:27 PM

Description

Add code to the mediawiki chart to allow suspending a job from values.yaml and/or from puppet

Details

Related Changes in Gerrit:

	Subject	Repo	Branch	Lines +/-
	mediawiki: Add mwcron.suspended_jobs list	operations/deployment-charts	master	+3 -1

Customize query in gerrit

Related Objects
Search...

Status	Assigned	Task
Resolved	dancy	T392693 Drop support for Debian Buster
Resolved	Clement_Goubert	T341560 Migrate mwmaint server functionality to mw-on-k8s
Resolved	Clement_Goubert	T341555 Implement periodic maintenance scripts for mw-on-k8s
Resolved	Clement_Goubert	T394409 Add a way to suspend CronJobs

Event Timeline

Clement_Goubert created this task.May 15 2025, 1:27 PM

Change #1146626 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):

[operations/deployment-charts@master] mediawiki: Add mwcron.suspended_jobs list

https://gerrit.wikimedia.org/r/1146626

gerritbot added a project: Patch-For-Review.May 15 2025, 1:35 PM

Copied from CR because it will need to be taken into account in further patches:

In https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/1146626, @kamila wrote:
From k8s docs:
Executions that are suspended during their scheduled time count as missed Jobs. When .spec.suspend changes from true to false on an existing CronJob without a starting deadline, the missed Jobs are scheduled immediately.
Should we also check for or set startingDeadlineSeconds to prevent surprises?

In https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/1146626, @Clement_Goubert wrote:

It's even worse than that, without startingDeadlineSeconds, if the CronJob has been suspended for more than 100 scheduled executions, then it won't start until it's deleted and recreated because of the missed schedules.

But for now I need a way to suspend a Job, we can sort out details in a later patch.