Installation from OperatorHub.io fails

[Avni-Sharma]

Minikube version

v1.16.0

What is the SBO version used?

0.7.1

What are the steps to reproduce this issue?

Follow the steps to install sbo on minikube from https://operatorhub.io/operator/service-binding-operator

What is the expected behaviour?

CSV of the SBO should be present and operator pod running

What is the actual behaviour?

Failing subscription

status:
  catalogHealth:
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: operatorhubio-catalog
      namespace: olm
      resourceVersion: "911"
      uid: 20f17516-805c-4fd0-805a-fcab38752723
    healthy: true
    lastUpdated: "2021-05-04T11:29:23Z"
  conditions:
  - lastTransitionTime: "2021-05-04T11:29:23Z"
    message: all available catalogsources are healthy
    reason: AllCatalogSourcesHealthy
    status: "False"
    type: CatalogSourcesUnhealthy
  lastUpdated: "2021-05-04T11:29:23Z"

Additional Information (Screenshots, etc)

k get subscriptions --all-namespaces
NAMESPACE   NAME                          PACKAGE                    SOURCE                  CHANNEL
operators   my-service-binding-operator   service-binding-operator   operatorhubio-catalog   beta

[pedjak]

@Avni-Sharma can you provide some more details? Like are pods created? I am not able to reproduce it on my instance. What is the output of

kubectl get packagemanifest | grep service-binding-operator

And what is the OLM version?

[Avni-Sharma]

kubectl get packagemanifest | grep service-binding-operator
service-binding-operator Community Operators 6m4s

[Avni-Sharma]

For OLM I used the step mentioned on the operatorhub.io
i.e
curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.18.0/install.sh | bash -s _v0.18.0

OLM - 0.18.0

[pedjak]

Oh, so the issue is with OLM 0.18, with 0.17 everything works fine. The problem is on OLM side, already reported in operator-framework/operator-lifecycle-manager#2129

Until the issue is fixed, we should use 0.17.0