Bug 2015022 - EUS Backport 4.6: OLM fails with 'ResolutionFailed' found more than one head for channel
Summary: EUS Backport 4.6: OLM fails with 'ResolutionFailed' found more than one head ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6.z
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Anik
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-18 09:09 UTC by Pamela Escorza
Modified: 2022-03-31 15:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-31 15:46:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pamela Escorza 2021-10-18 09:09:12 UTC
Description of problem:
+++ This bug was initially created as a clone of Bug 1969902 +++

Version-Release number of selected component (if applicable):
OCP 4.6 EUS


Steps to Reproduce:
* Unknown what the *exact* process on the customer side is to update the images
* Update catalog with new version of Operator

Actual results:
Mutilple events like: 
"type: 'Warning' reason: 'ResolutionFailed' found more than one head for channel" on OCP 4.6 

Expected results:
Not to have those warning events.

Comment 59 Anik 2022-03-31 15:46:21 UTC
That's great news. I'm going to assume that changing the channel will fix Poornima's CU's events too. 

Since the problem of the error message not being clear in what the problem actually is is solved in latest olm as part of https://github.com/operator-framework/operator-lifecycle-manager/pull/2260, I am going to close this bug report.


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