action #121225
bot-ng - synchronize pipeline fails on GitLab size:S
Start date:
2021-09-02
Due date:
% Done:
0%
Estimated time:
Tags:
Description
The the following recent failures:
- https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipelines/540242
- https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipelines/540243
- https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipelines/540484
- https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipelines/540508
- https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1272283
Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/qa-maintenance/bot-ng/.git/ Created fresh repository. fatal: unable to access 'https://gitlab.suse.de/qa-maintenance/bot-ng.git/': The requested URL returned error: 500
Acceptance criteria¶
- AC1: bot-ng synchronize is executed successfully
Suggestions¶
- This occurred outside the maintenance window - we can't assume it'll go away?
- Inform INFRA about the issue and make sure it doesn't happen anymore
History
#1
Updated by robert.richardson 2 months ago
- Subject changed from bot-ng - synchronize pipeline fails on GitLab to bot-ng - synchronize pipeline fails on GitLab size:S
- Description updated (diff)
- Status changed from New to Workable
#5
Updated by cdywan 2 months ago
osukup wrote:
Also failed twice whilst cloning from GitHub now:
$ git clone --depth 1 https://github.com/openSUSE/qem-bot.git ++ echo '$ git clone --depth 1 https://github.com/openSUSE/qem-bot.git' ++ git clone --depth 1 https://github.com/openSUSE/qem-bot.git Cloning into 'qem-bot'... fatal: early EOF fatal: fetch-pack: invalid index-pack output
#6
Updated by okurz about 2 months ago
- Tags changed from reactive work to reactive work, infra
#7
Updated by cdywan about 2 months ago
- Copied to action #121846: openQABot - schedule:openqabot pipeline fails on GitLab size:S added
#8
Updated by jbaier_cz about 2 months ago
- Copied to deleted (action #121846: openQABot - schedule:openqabot pipeline fails on GitLab size:S)
#9
Updated by okurz about 2 months ago
- Status changed from Blocked to Resolved
- Assignee changed from osukup to cdywan
gitlab CI runner was downgraded which likely fixed the problem. We didn't observe the above problem again lately