action #130952
closed
[alert][thursday] gitlab.suse.de CI jobs fail with "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500" as of 2023-06-15 size:M
Added by okurz 11 months ago.
Updated 9 months ago.
Description
Observation¶
https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1634181 failed with
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected flush after ref listing
I assume it's a current problem in Eng-Infra maintained infrastructure or OBS
Acceptance criteria¶
- AC1: Stable gitlab CI pipelines again with no errors about accessing other ressources like registry, gitlab, OBS/IBS, etc.
Suggestions¶
- Check for related gitlab CI pipeline failures
- If issue persists over "usual thursday maintenance window" problems then create SUSE-IT ticket
- For SUSE-IT ticket resolution ensure all our "usual" gitlab CI pipelines are stable again
- Subject changed from [alert][thursday] gitlab.suse.de CI jobs fail with "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500" as of 2023-06-15 to [alert][thursday] gitlab.suse.de CI jobs fail with "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500" as of 2023-06-15 size:M
- Description updated (diff)
- Status changed from New to In Progress
- Status changed from In Progress to Workable
- Assignee deleted (
okurz)
- Status changed from Workable to Resolved
- Assignee set to okurz
- Status changed from Resolved to In Progress
happened again today outside of usual Thursday maintenance window in https://gitlab.suse.de/openqa/openqa-review/-/jobs/1656553 with
$ git clone --depth 1 https://github.com/os-autoinst/openqa_review.git
Cloning into 'openqa_review'...
error: RPC failed; HTTP 408 curl 22 The requested URL returned error: 408
fatal: expected flush after ref listing
- Due date set to 2023-07-11
- Status changed from In Progress to Feedback
I need to check again where the retry command should come from.
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Due date deleted (
2023-07-11)
- Status changed from Feedback to Resolved
- Status changed from Resolved to In Progress
- Status changed from In Progress to Blocked
- Priority changed from Urgent to High
SD ticket was now being picked up and is worked on
- Status changed from Blocked to Resolved
Should be fine. Meanwhile gitlab is running from PRG2 so fresh start with a new chance for stability :)
Also available in: Atom
PDF