Project

General

Profile

Actions
Copy link

action #133454

closed

bot-ng - pipelines in GitLab fail to pull qam-ci-leap:latest size:M

Added by livdywan 9 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
High
Assignee:
livdywan
Target version:
openQA Project - Ready
Start date:
Due date:
2023-09-08
% Done:

0%

Estimated time:
Tags:
infra

Description

Observation

The the following recent failures:

WARNING: Failed to pull image with policy "always": Error response from daemon: unknown: SSL_connect error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number (manager.go:237:0s)
ERROR: Job failed: failed to pull image "registry.suse.de/qa/maintenance/containers/qam-ci-leap:latest" with specified policies [always]: Error response from daemon: unknown: SSL_connect error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number (manager.go:237:0s)

Acceptance criteria

  • AC1: bot-ng pipelines are executed successfully repeatedly

Suggestions

  • The jobs fail well before any script execution so nothing we control within .gitlab-ci.yml, or can we?
  • Research upstream what can be done if the initial container image download fails. Maybe we can specify a retry for what the executor is trying to pull. Or we spawn an internal super-mini image and in there call the container pull nested
  • Report SD ticket that they should fix the infrastructure

Related issues 1 (0 open — 1 closed)

Copied from QA - action #123064: bot-ng - pipelines in GitLab fail to pull qam-ci-leap:latestResolvedlivdywan2021-09-022023-03-05

Actions
Actions
Copy link
 #1

Updated by livdywan 9 months ago

  • Copied from action #123064: bot-ng - pipelines in GitLab fail to pull qam-ci-leap:latest added
Actions
Copy link
 #2

Updated by okurz 9 months ago

  • Tags set to infra

please add "infra" tags for such issues

Actions
Copy link
 #3

Updated by okurz 9 months ago

  • Subject changed from bot-ng - pipelines in GitLab fail to pull qam-ci-leap:latest to bot-ng - pipelines in GitLab fail to pull qam-ci-leap:latest size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #4

Updated by livdywan 9 months ago

  • Status changed from Workable to In Progress
  • Assignee set to livdywan

As we've not seen failures recently we may not be able to test it but it's still useful as a research task. So as discussed on Jitsi I'm looking into a proof of concept of the container idea without spending too much time on it.

Actions
Copy link
 #5

Updated by openqa_review 9 months ago

  • Due date set to 2023-08-25

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #6

Updated by okurz 9 months ago

  • Due date changed from 2023-08-25 to 2023-09-08
  • Status changed from In Progress to Feedback

Discussed in weekly tools team meeting. gitlab has moved to PRG2 so maybe the error will not effectively happen again. I suggest you just wait some days/weeks if the error reproduces.

Actions
Copy link
 #7

Updated by livdywan 8 months ago

  • Status changed from Feedback to Resolved

I think we're actually fine here at this point. Of course we can always re-open if needed.

Actions
Copy link

Also available in: Atom PDF