Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1785674

Summary:	[Upgrade] 4.2.12 -> 4.3.0-0.nightly-2019-12-18-105351 upgrade stuck at 77% - olm-operator crash looping
Product:	OpenShift Container Platform	Reporter:	Evan Cordell <ecordell>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OLM	QA Contact:	Mike Fiedler <mifiedle>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	ccoleman, ecordell, erich, jiazha, lmohanty, mifiedle, wking
Version:	4.4	Keywords:	Reopened, TestBlocker
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1784915	Environment:
Last Closed:	2020-05-04 11:20:55 UTC	Type:	---
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:	1784915

Comment 3 W. Trevor King 2020-01-31 17:13:23 UTC

I am very confused by ON_QA -> ASSIGNED -> CLOSED ERRATA.  This was initially cloned from the 4.3-targeting bug 1784915.  That was fixed (as far as I can tell) by [1].  [1] was the 4.3 backport of the 4.4 [2].  [2] claims it was fixing this bug, but only after it merged (so the Bugzilla Prow plugin was no longer watching) [3].  So I'm manually linking the fixing PR and moving back to MODIFIED so the Errata sweeper can move it back to ON_QA.

[1]: https://github.com/operator-framework/operator-lifecycle-manager/pull/1208
[2]: https://github.com/operator-framework/operator-lifecycle-manager/pull/1207
[3]: https://github.com/operator-framework/operator-lifecycle-manager/pull/1207#event-2901256490

Comment 5 Mike Fiedler 2020-01-31 19:46:04 UTC

Verified on 4.4.0-0.nightly-2020-01-31-115654 (This bz is targeted for 4.4)

olm-operator deployment has no resource limits:

        resources:
          requests:
            cpu: 10m
            memory: 160Mi

Comment 7 errata-xmlrpc 2020-05-04 11:20:55 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