Bug 1942522 - Resolution fails to sort channel if inner entry does not satisfy predicate
Summary: Resolution fails to sort channel if inner entry does not satisfy predicate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.8
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.8.0
Assignee: Ben Luddy
QA Contact: Salvatore Colangelo
URL:
Whiteboard:
Depends On:
Blocks: 1951232
TreeView+ depends on / blocked
 
Reported: 2021-03-24 13:50 UTC by Trey West
Modified: 2022-10-11 06:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1951232 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:55:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift operator-framework-olm pull 60 0 None open Bug 1942522: Fix resolution error if inner entry doesn't provide a required API. 2021-04-19 20:27:04 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:55:34 UTC

Description Trey West 2021-03-24 13:50:14 UTC
Description of problem:

When installing Assisted service community operator from operatorhub, installation hangs and no resources are created in assisted-installer namespace.

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


How reproducible:

100%


Steps to Reproduce:
1. Create IPv4 hub cluster
2. Complete prerequisite for operator (pvcs, install hive operator)
3. Install assisted service operator through operatorhub.

Actual results:

Assisted service operator installation hangs and shows loading wheel indefinitely. No resources are created in assisted-installer namespace.


Expected results:

Assisted service operator installs, assisted service comes up and UI is reachable.


Additional info:

Comment 1 Trey West 2021-03-24 14:02:41 UTC
May be an issue with the way dependencies on hive operator are being handled:

[root@sealusa54 ~]# oc get events -n default
LAST SEEN   TYPE      REASON             OBJECT                         MESSAGE
102s        Warning   ResolutionFailed   namespace/assisted-installer   found multiple channel heads: [hive-operator.v1.0.19 hive-operator.v1.0.4], please check the `replaces`/`skipRange` fields of the operator bundles
108s        Warning   ResolutionFailed   namespace/assisted-installer   found multiple channel heads: [hive-operator.v1.0.17 hive-operator.v1.0.4], please check the `replaces`/`skipRange` fields of the operator bundles

Comment 8 Salvatore Colangelo 2021-04-20 21:46:30 UTC
Hi 

below the step .

1. From operator hub install Assisted Service Operator


2. Verify if the operator is installed correctly 

[scolange@scolange go]$ oc -n assisted-installer get sub
NAME                        PACKAGE                     SOURCE                CHANNEL
assisted-service-operator   assisted-service-operator   community-operators   alpha


[scolange@scolange go]$ oc -n assisted-installer get csv
NAME                               DISPLAY                            VERSION    REPLACES                           PHASE
assisted-service-operator.v0.0.2   Assisted Service Operator          0.0.2      assisted-service-operator.v0.0.1   Succeeded
elasticsearch-operator.5.0.2-27    OpenShift Elasticsearch Operator   5.0.2-27                                      Succeeded

NAME            CSV                                APPROVAL    APPROVED
install-99hq2   assisted-service-operator.v0.0.2   Automatic   true


LGMT!

Comment 11 errata-xmlrpc 2021-07-27 22:55:12 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438


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