Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1440202 - [3.5] Image pruning may incorrectly delete an image if it has both weak and strong references
[3.5] Image pruning may incorrectly delete an image if it has both weak and s...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry (Show other bugs)
3.5.0
Unspecified Unspecified
urgent Severity urgent
: ---
: ---
Assigned To: Maciej Szulik
ge liu
:
Depends On: 1439926
Blocks: 1440177 1440197 1440199 1440201
  Show dependency treegraph
 
Reported: 2017-04-07 10:33 EDT by Maciej Szulik
Modified: 2017-07-24 10 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Logic error in how weak and strong references are identified when searching images eligible for pruning. Consequence: Some images having both strong and weak references in pruning graph could be removed during pruning. Fix: Fix logic responsible for finding which images have strong references. Result: Pruning correctly recognizes and prunes images.
Story Points: ---
Clone Of: 1439926
Environment:
Last Closed: 2017-04-12 15:15:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2995561 None None None 2017-04-11 16:19 EDT
Red Hat Product Errata RHBA-2017:0884 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 18:50:07 EDT

  None (edit)
Comment 15 Wang Haoran 2017-04-10 10:28:46 EDT
Mark verified, and use this[1] to track another issue

[1]https://github.com/openshift/origin/issues/13700
Comment 18 errata-xmlrpc 2017-04-12 15:15:12 EDT
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:0884

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