-
Bug
-
Resolution: Done
-
Blocker
-
Pipelines 1.6.1
-
None
-
2
-
False
-
False
-
pipelines-webhook and pipelines-controller pod are going to CrashLoopBackOff
Steps to Reproduce:
- Install OpenshiftPipelines operator 1.6.0 using the index image quay.io/openshift-pipeline/redhat-operator-index:v4.9-2111290727
- Once the tektonconfig config CR gets the status as True, upgrade the Openshift Pipelines operator to 1.6.1 using the index image registry.redhat.io/redhat/redhat-operator-index:v4.9
- Once the tektonconfig config CR gets the status as True, upgrade the Openshift Pipelines operator to 1.6.2 using the index image quay.io/openshift-pipeline/redhat-operator-index:172579
- Observe the status of pods in openshift-pipelines namespace
Expected Behaviour:
All the pods in the openshift-pipelines namespace should be running and the status of tektonconfig config CR should be True
Actual Behaviour:
The pipelines-webhook and pipelines-controller pod are going to CrashLookBackOff
Logs:
$ kubectl logs -n openshift-pipelines tekton-pipelines-controller-649f4bd7f6-x4dpc
2022/02/08 09:47:31 Registering 7 clients
2022/02/08 09:47:31 Registering 5 informer factories
2022/02/08 09:47:31 Registering 11 informers
2022/02/08 09:47:31 Registering 2 controllers
2022/02/08 09:47:31 Readiness and health check server listening on port 8080
2022/02/08 09:47:36 Error reading/parsing logging configuration: timed out waiting for the condition: Unauthorized