Actions
action #179038
closedcoordination #154777: [saga][epic] Shareable os-autoinst and test distribution plugins
coordination #162131: [epic] future version control related features in openQA
Gracious handling of longer remote git clones outages size:S
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2025-03-17
Due date:
2025-04-11
% Done:
0%
Estimated time:
Description
Motivation¶
Currently, git_clone minion jobs fail when GitLab is temporarily unreachable (see #178492), by introducing a proper error-handling mechanism, we can ensure:
- Temporary outages do not cause unnecessary job failures or alerts.
User Story¶
"As a test engineer and openQA operator,
i want openQA to handle short-lived GitLab outages without causing mass Minion job failures,
so that users do not experience unnecessary disruption
Acceptance Criteria¶
- AC1: Temporary remote git outages don't cause failing minion jobs
- AC2: An update of remote git repositories is still ensured on shorter failed requests, e.g. in range of seconds
Suggestions¶
- Damage is likely limited. If we can't sync needles nobody can edit needles.
- Jobs end up incomplete if there's an on-going issue with git_clone minion jobs
- We could decide to eventually give up and continue anyway and let jobs run
Updated by robert.richardson about 1 month ago
- Related to action #178492: [alert] Many failing `git_clone` Minion jobs auto_review:"Error detecting remote default branch name":retry size:S added
Updated by okurz about 1 month ago
- Target version changed from Ready to Tools - Next
Updated by okurz about 1 month ago
- Subject changed from Improve GitLab Outage Handling in openQA to Gracious handling of longer remote git clones outages size:S
- Description updated (diff)
Updated by okurz about 1 month ago
- Copied to action #179185: Detection of long-time remote git clone outages size:S added
Updated by okurz about 1 month ago
- Status changed from New to Workable
- Target version changed from Tools - Next to Ready
Needed for #178492
Updated by robert.richardson about 1 month ago
- Assignee set to robert.richardson
Updated by robert.richardson 30 days ago
- Status changed from Workable to In Progress
Updated by openqa_review 29 days ago
- Due date set to 2025-04-08
Setting due date based on mean cycle time of SUSE QE Tools
Updated by robert.richardson 13 days ago
- Status changed from In Progress to Feedback
Updated by livdywan 12 days ago
- Copied to action #180863: Conduct lessons learned "Five Why" analysis for "Gracious handling of longer remote git clones outages" size:S added
Actions