Description of problem: Independently of each dependency an Operator have, AWS S3 bucket Operator is being installed and not the required Operators declared in CSV. For example, Kogito Operator has Infinispan and Keycloak as a dependency, after installing it using Operator Hub, the following csv are installed: oc get csv -n test-operators NAME DISPLAY VERSION REPLACES PHASE awss3operator.1.0.0 AWS S3 Operator 1.0.0 Succeeded kogito-operator.v0.13.0 Kogito 0.13.0 kogito-operator.v0.12.0 Pending oc get csv kogito-operator.v0.13.0 -o yaml -n test-operators phase: Pending reason: RequirementsNotMet requirementStatus: - group: apiextensions.k8s.io kind: CustomResourceDefinition message: CRD is present and Established condition is true name: infinispans.infinispan.org status: Present uuid: 8082dec1-251f-48b5-92d7-c0632feb3533 version: v1 - group: apiextensions.k8s.io kind: CustomResourceDefinition message: CRD is present and Established condition is true name: kafkas.kafka.strimzi.io status: Present uuid: 85ce9e95-3122-4d3f-81d0-eec4988638b1 version: v1 - group: apiextensions.k8s.io kind: CustomResourceDefinition message: CRD is present and Established condition is true name: kafkatopics.kafka.strimzi.io status: Present uuid: 1537aa87-94f7-4986-930d-602fc9b13a0d version: v1 - group: apiextensions.k8s.io kind: CustomResourceDefinition message: CRD is not present name: keycloaks.keycloak.org status: NotPresent version: v1 Note: I found more operators with the same issue Version-Release number of selected component (if applicable): OCP 4.6.0-0.nightly-2020-08-18-165040 OLM version: 0.16.0 git commit: 1fdd347ab723bf6aec30c79dfb217bcbf21a13e9 How reproducible: Always Steps to Reproduce: 1. Install an Operator that has dependencies Actual results: 1. OLM is installing wrong dependency Expected results: 1 OLM should install the dependencies mentioned as required in CSV Additional info:
Hey Bruno, So there are a few issues here. I would like to ask you to retest this bug with a new 4.6 cluster (the latest build possible) as there is a recent fix on operator-registry (https://github.com/operator-framework/operator-registry/pull/417). The community index image was just rebuilt 3 hour so it may have contained this issue. You should expect the kogito-operator fail to get installed as nothing happens. No CSV or installplan created. Please verify this. The second issue here is OLM fails to resolve dependency due to another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1869441. We are currently working on that bug and when it is resolved, you should see kogito-operator get installed correctly with its dependencies. Thanks, Vu