Bug 1499643 - [3.5] Image pruning fails due to conflicts on imagestream updates
Summary: [3.5] Image pruning fails due to conflicts on imagestream updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5.z
Assignee: Michal Minar
QA Contact: Dongbo Yan
URL:
Whiteboard:
Depends On: 1491020
Blocks: 1499640
TreeView+ depends on / blocked
 
Reported: 2017-10-09 07:40 UTC by Michal Minar
Modified: 2021-03-11 15:56 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: the pruner and some other subject modified the same image stream at the same time Consequence: the image pruner stopped and failed because of the conflict Fix: image pruner now retries to update the image stream on conflict Result: image pruner is tolerant to conflicts
Clone Of: 1491020
Environment:
Last Closed: 2017-10-25 13:08:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3049 0 normal SHIPPED_LIVE OpenShift Container Platform 3.6, 3.5, and 3.4 bug fix and enhancement update 2017-10-25 15:57:15 UTC

Comment 2 Michal Minar 2017-10-10 16:39:15 UTC
PR: https://github.com/openshift/ose/pull/896

Comment 4 Dongbo Yan 2017-10-13 08:04:58 UTC
wait for available puddle

Comment 6 Dongbo Yan 2017-10-16 11:48:15 UTC
Verified
$ ./oc version
oc v3.5.5.31.36
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO

cannot reproduce this issue

Comment 8 errata-xmlrpc 2017-10-25 13:08: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/RHBA-2017:3049


Note You need to log in before you can comment on or make changes to this bug.