Current workaround:
tools.wikibugs@tools-sgebastion-10:~$ kubectl get pods NAME READY STATUS RESTARTS AGE grrrrit-654c5cbbf-gc4ns 1/1 Running 0 16m redis2irc-7bbc8dc544-kms8k 1/1 Running 0 3m27s wikibugs-phab-858dbb66fb-vvldc 1/1 Running 0 16m tools.wikibugs@tools-sgebastion-10:~$ kubectl delete pod redis2irc-7bbc8dc544-kms8k
but needing to use kubectl directly is not very convenient.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • JHedden | T251027 "signatures" tool has failed job pods on Kubernetes cluster | |||
| Resolved | aborrero | T251917 Design the Jobs service in k8s | |||
| Resolved | aborrero | T283238 Toolforge: develop jobs-framework-api | |||
| Resolved | aborrero | T285944 Toolforge: beta phase for the new jobs framework | |||
| Resolved | Feature | taavi | T306311 toolforge-jobs should have a method to easily restart a specific job |
Change 821196 had a related patch set uploaded (by Majavah; author: Majavah):
[cloud/toolforge/jobs-framework-api@main] add restart endpoint
Noting here that the new API endpoint currently also will start a new execution of a cron job, even if it wasn't already running. This is explicitly an unsupported implementation detail that may change in the future.
Change 821196 merged by jenkins-bot:
[cloud/toolforge/jobs-framework-api@main] add restart endpoint
Change 841176 had a related patch set uploaded (by Majavah; author: Majavah):
[cloud/toolforge/jobs-framework-cli@master] Add restart subcommand
Change 843882 had a related patch set uploaded (by Majavah; author: Majavah):
[cloud/toolforge/jobs-framework-api@main] restart: don't permit starting cron jobs which are not running
Change 843882 merged by jenkins-bot:
[cloud/toolforge/jobs-framework-api@main] restart: don't permit starting cron jobs which are not running
Change 841176 merged by jenkins-bot:
[cloud/toolforge/jobs-framework-cli@master] Add restart subcommand