Actions
action #99333
closedqa-maintenance/openQABot CI job fails after max retries to reach germ159.suse.cz
Start date:
2021-09-27
Due date:
2022-01-31
% Done:
0%
Estimated time:
Description
Observation¶
https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/609314#L177 fails after max retries to reach germ159.suse.cz. Why does openQABot even try to reach that host?
Steps to reproduce¶
Failed multiple times during the past days, e.g. in
- https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/609408
- https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/609314
- https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/609220
- https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/608936
- https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/608685
likely every job for PTFs (L3) is failing.
Problem¶
- Why do we even try to reach that host? This seems to be related to PTFs, see update/ptf.py
Suggestions¶
- DONE: Disable CI schedule until fixed
- Longer and more retries, especially when using something like a non-production machine
- Find a production machine (proper hostname) for this task
- Re-enable CI schedule in https://gitlab.suse.de/qa-maintenance/openQABot/-/pipeline_schedules
Rollback steps¶
- Re-enable CI schedule in https://gitlab.suse.de/qa-maintenance/openQABot/-/pipeline_schedules
Actions