Project

General

Profile

action #72316

[tests][ci] circleci can fail in `zypper ref` due to temporary repository problems

Added by okurz 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Concrete Bugs
Target version:
Start date:
2020-06-09
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

https://app.circleci.com/pipelines/github/os-autoinst/openQA/4431/workflows/71688235-bc92-4d9f-9185-15747b8d3d90/jobs/42467

+ sudo zypper --gpg-auto-import-keys ref
Retrieving repository 'devel' metadata [\]error]
Repository 'devel' is invalid.
[devel|http://download.opensuse.org/repositories/devel:openQA/openSUSE_Leap_15.1] Valid metadata not found at specified URL
History:
 - [|] Error trying to read from 'http://download.opensuse.org/repositories/devel:openQA/openSUSE_Leap_15.1'
 - Timeout exceeded when accessing 'http://download.opensuse.org/repositories/devel:openQA/openSUSE_Leap_15.1/content'.

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'devel' because of the above error.
Retrieving repository 'openQA' metadata [|]error]
Repository 'openQA' is invalid.

Acceptance criteria

  • AC1: Retries are conducted if refreshing the repository fails one time

Suggestions

  • Add a retry for the zypper ref call

Related issues

Copied from openQA Project - action #67855: [tests][ci] circleci often abort in "cache" unable to read container image from registry.opensuse.orgNew2020-06-09

History

#1 Updated by okurz 10 months ago

  • Copied from action #67855: [tests][ci] circleci often abort in "cache" unable to read container image from registry.opensuse.org added

#2 Updated by okurz 10 months ago

  • Status changed from In Progress to Feedback

#3 Updated by okurz 10 months ago

  • Status changed from Feedback to Resolved

PR merged. Unlikely we see this problem soon or would be able to find places where this happened. We would only see this if my approach was wrongly done or does not help in which case we should reopen the ticket.

Also available in: Atom PDF