Bug 1785674 - [Upgrade] 4.2.12 -> 4.3.0-0.nightly-2019-12-18-105351 upgrade stuck at 77% - olm-operator crash looping
Summary: [Upgrade] 4.2.12 -> 4.3.0-0.nightly-2019-12-18-105351 upgrade stuck at 77% - ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Evan Cordell
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks: 1784915
TreeView+ depends on / blocked
 
Reported: 2019-12-20 16:22 UTC by Evan Cordell
Modified: 2020-05-04 11:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1784915
Environment:
Last Closed: 2020-05-04 11:20:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-lifecycle-manager pull 1207 0 None closed Bug 1785674: fix(deploy): remove resource limits 2020-08-31 13:59:21 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:21:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.