Bug 1825284 - Image Pruner Automatically Installed on Upgrade
Summary: Image Pruner Automatically Installed on Upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Corey Daley
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks: 1826033
TreeView+ depends on / blocked
 
Reported: 2020-04-17 14:53 UTC by Adam Kaplan
Modified: 2020-07-13 17:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1826033 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:28:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:28:54 UTC

Description Adam Kaplan 2020-04-17 14:53:03 UTC
Description of problem:

The new auto image pruning feature is automatically installed on upgrade.
Per the enhancement, customers should be able to opt-in to image pruning on upgrade.


Version-Release number of selected component (if applicable): 4.5.0


How reproducible: Always


Steps to Reproduce:
1. Launch a 4.4.0 cluster
2. Force an upgrade to a 4.5.0 nightly
3. Look for image pruner resources in the openshift-image-registry namespace

Actual results:

Image pruner resource is created with default parameters.


Expected results:

Image pruner does not exist.


Additional info:

https://github.com/openshift/enhancements/blob/master/enhancements/image-registry/automate-pruning.md

Comment 4 Adam Kaplan 2020-04-20 20:17:01 UTC
Marking this as VERIFIED for 4.5.0 - this is implementing the correct upgrade behavior where new installs have the pruner enabled.

Comment 6 errata-xmlrpc 2020-07-13 17:28:32 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-2020:2409


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