CLI-based install of Kuadrant Operator hangs with status Unknown

[smccarthy-ie]

Installing the Kuadrant Operator on OpenShift 4.16 and AWS using the install instructions gives error executing jsonpath instead of complete:

$ kubectl apply -f - <<EOF                                                    	 
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: kuadrant-operator
  namespace: kuadrant-system
spec:
  channel: preview
  installPlanApproval: Automatic
  name: kuadrant-operator
  source: kuadrant-operator-catalog
  sourceNamespace: kuadrant-system
---
kind: OperatorGroup
apiVersion: operators.coreos.com/v1
metadata:
  name: kuadrant
  namespace: kuadrant-system
spec:
  upgradeStrategy: Default
EOF
subscription.operators.coreos.com/kuadrant-operator created
operatorgroup.operators.coreos.com/kuadrant created

$ kubectl get installplan -n kuadrant-system -o=jsonpath='{.items[0].status.phase}'
error: error executing jsonpath "{.items[0].status.phase}": Error executing template: array index out of bounds: index 0, length 0. Printing more information for debugging the template:
	template was:
    	{.items[0].status.phase}
	object given to jsonpath engine was:
    	map[string]interface {}{"apiVersion":"v1", "items":[]interface {}{}, "kind":"List", "metadata":map[string]interface {}{"resourceVersion":""}}

Changing the channel to stable made no difference.

The Operator hangs in the OCP web console with status Unknown and CatalogSource not found:

The Conditions table displays the following error under ResolutionFailed:

constraints not satisfiable: no operators found from catalog kuadrant-operator-catalog in namespace 
kuadrant-system referenced by subscription kuadrant-operator, subscription kuadrant-operator exists

[eguzki]

Yes, one of the dependencies (limitador operator especifically) was not released in 4.16. We limited to 4.12-4.14. We are working on a new release of kuadrant on the public OLM catalogs that fixes that with the latest release of kuadrant (v0.10.0). You are trying to install 0.7.1 ;)

It should be a matter of few (working) days.

[eguzki]

BTW, you already have kuadrant v0.10.0 for bare kubernetes in operatorhub.io. Just not in Openshift community catalog yet.

[smccarthy-ie]

Thanks @eguzki, that's very helpful info, will try on OCP 4.14 instead.

Also makes sense now why trying to install using OCP v4.16 web console selects Kuadrant v0.72, hangs with status Unknown, and Conditions table displays the following under ResolutionFailed :)

constraints not satisfiable: bundle kuadrant-operator.v0.7.2 requires an operator with package: 
limitador-operator and with version in range: 0.8.0, subscription kuadrant-operator exists, subscription 
kuadrant-operator requires community-operators/openshift-marketplace/stable/kuadrant-operator.v0.7.2

Looking forward to trying this again when fixed for OCP 4.16 and Kuadrant 0.10.0.