-
Bug
-
Resolution: Done
-
Critical
-
Pipelines 1.8.0
-
None
-
False
-
None
-
False
Expected behavior
OpenShift Pipelines operator 1.8 can be installed on OpenShift 4.12
Actual behavior
Operator pod fails to download image, I verified that the image exists and can be pulled on local machine
Failed to pull image "registry.redhat.io/openshift-pipelines/pipelines-rhel8-operator@sha256:5b0075fc5ca3b729f2308c3237896cee2965be7613837356b56e6ceefbbe6416": rpc error: code = Unknown desc = copying system image from manifest list: reading signatures: parsing signature https://registry.redhat.io/containers/sigstore/openshift-pipelines/pipelines-rhel8-operator@sha256=9314e491b95c6995b3fe060be699d0f2ca7c37998f9bd8f9a7478f1c4fb78c13/signature-7: unrecognized signature format, starting with binary 0x3c
After couple of minutes, operator pod and webhook pod are running but nothing appears in openshift-pipelines namespace. Operator pod contains messages like this
{"level":"info","logger":"tekton-operator-cluster-operations.event-broadcaster","caller":"record/event.go:285","msg":"Event(v1.ObjectReference{Kind:\"TektonInstallerSet\", Namespace:\"\", Name:\"pipeline-c5s2f\", UID:\"30f4bb71-93fb-4fdc-a51d-13e9977e0b53\", APIVersion:\"operator.tekton.dev/v1alpha1\", ResourceVersion:\"42989\", FieldPath:\"\"}): type: 'Warning' reason: 'InternalError' no matches for kind \"HorizontalPodAutoscaler\" in version \"autoscaling/v2beta1\"","commit":"ea77baf","knative.dev/pod":"openshift-pipelines-operator-7ccb488cb-869hp"}
$ oc get tektoninstallerset NAME READY REASON pipeline-c5s2f False Error prepipeline-zdn4p True rhosp-rbac-25ncx True validating-mutating-webhoook-kspmn True
Steps to reproduce
1. Install a nightly build of OpenShift 4.12
2. Install Pipelines operator