Bug 1811204 - upgrades where entire sample imagestreams were removed in the new version can get stuck in progressing
Summary: upgrades where entire sample imagestreams were removed in the new version can...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Samples
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: Gabe Montero
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On: 1811143
Blocks: 1811206
TreeView+ depends on / blocked
 
Reported: 2020-03-06 20:26 UTC by Gabe Montero
Modified: 2020-05-04 11:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: if a sample imagestream available in a prior release was removed in a subsequent release, then during upgrade to that subsequent releast the removed imagestream could be incorrectly tracked as needing imagestreamimports to complete, and since no imagestreamimmports are even occurring, samples will not report its upgrade as complete Consequence: overall upgraded would be marked as failed if the problematic timing windows in samples operator occured Fix: samples operated was updated to not attempt to track imagestreams which existed in a prior release but not in the release we are upgrading to Result: imagestreams that are removed release to release should not cause samples operator to fail upgrade
Clone Of: 1811143
Environment:
Last Closed: 2020-05-04 11:45:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-samples-operator pull 242 0 None closed [release-4.4] Bug 1811204: purge removed imagestreams as a part of upgrade from progessing/impor… 2020-11-26 15:45:59 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:46:11 UTC

Comment 1 Gabe Montero 2020-03-19 15:26:29 UTC 
PR https://github.com/openshift/cluster-samples-operator/pull/242 is up but we have bugzilla bot hoopla about this PR targeting 4.4.z instead of 4.4
Comment 2 Gabe Montero 2020-04-13 17:56:33 UTC 
per discussion with Adam, setting target for 4.4.0

will let patch managers make final call on inclusion
Comment 8 XiuJuan Wang 2020-04-23 02:00:58 UTC 
Upgrade from 4.3.14 to 4.4.0-0.nightly-2020-04-21-210658
Samples operator upgrade successfully, and passed the regression test.
Comment 10 errata-xmlrpc 2020-05-04 11:45:36 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:0581
Note You need to log in before you can comment on or make changes to this bug.