Actions
action #108980
opencoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #96263: [epic] Exclude certain Minion tasks from "Too many Minion job failures alert" alert
coordination #99831: [epic] Better handle minion tasks failing with "Job terminated unexpectedly"
Better handle minion tasks failing with "Job terminated unexpectedly" - OpenQA::Task::Asset::Download
Start date:
2022-03-25
Due date:
% Done:
0%
Estimated time:
Description
Acceptance criteria¶
- AC1: minion job "download_asset" has a sigterm handler to decide how to shut down in a clean way in a reasonable time
- AC2: Our minion job list on OSD and O3 do not show any "Job terminated unexpectedly" over multiple deployments for "download_asset"
Suggestions¶
- Implement sigterm handler for "download_asset" like it has already been done for other jobs (e.g. #103416)
- Test on o3 and osd either by manually restarting openqa-gru multiple times or awaiting the result from multiple deployments and checking the minion dashboard, e.g. openqa.suse.de/minion/jobs?state=failed
Updated by tinita 3 months ago
- Related to action #167797: scripts-ci multimachine test CI job fails due to job incompleting with "minion failed" size:M added
Updated by tinita about 2 months ago
- Copied to action #169144: Link to minion job from openQA job with waiting task added
Actions