Bug 1752775

Summary:	Skopeo doesn't handle HTTP 429 errors properly
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Bašti <mbasti>
Component:	skopeo	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.8	CC:	ddarrah, dwalsh, jpaulovi, lkolacek, mfaruga, tsweeney, twaugh, yujiang
Target Milestone:	rc	Keywords:	Extras
Target Release:	7.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1813295 (view as bug list)		Environment:
Last Closed:	2020-04-01 00:26:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1813295

Description Martin Bašti 2019-09-17 08:22:23 UTC

Description of problem:
Skopeo doesn't handle HTTP 429 errors properly.
https://github.com/containers/image/issues/618

Version-Release number of selected component (if applicable):
all + upstream


How reproducible:


Steps to Reproduce:
1. https://github.com/containers/image/issues/618#issuecomment-531161085
2. run skopeo inspect against proxy in 1.
3.

Actual results:
Skopeo fails with server error 429


Expected results:
Skopeo retries query with proper backoff time


Additional info:
Also RHEL7 and Fedora releases should be fixed by backport

Comment 3 Valentin Rothberg 2019-10-21 15:40:16 UTC

The issue is now fixed in the containers/image library and will be available with the next version of Skopeo.

Comment 5 Daniel Walsh 2019-10-30 20:14:36 UTC

RHEL 8.1.1 and RHEL8.2 should get that release.

Comment 6 Daniel Walsh 2019-10-30 20:15:42 UTC

Jindrich can you prepare new version of Skopeo for release in 8.1.1 and 8.2?

Comment 17 errata-xmlrpc 2020-04-01 00:26:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1230