Actions
action #125531
closedsalt-pillar C pipeline runs into 1h timeout
Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2023-03-07
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/1441277 fails with "The script exceeded the maximum execution time set for the job" after 1h.
Acceptance criteria¶
- AC1: salt-pillar CI jobs take significantly less than 2h
- AC2: salt-pillar CI jobs do not commonly fail due to gitlab CI timeout
Suggestions¶
- Try to just bump the timeout
- Look into the history of previous jobs how long it usually takes to apply the salt pillar triggered high state
- Find out if there are specific machines that are problematic
Updated by okurz almost 2 years ago
- Status changed from New to Resolved
- Assignee set to okurz
- Target version changed from future to Ready
should be addressed by https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/803 from fniederwanger. It might be that this really is necessary as we have more hosts and more stuff going on in salt and multiple problems in particular with repos on download.opensuse.org but it might also be that specific hosts are problematic. We don't know from gitlab CI logs as they are not available due to the timeout but logs on salt master and minions would actually tell.
Actions