Closed dwojciec closed 5 years ago
Problem solved. I deployed the Openshift Pipelines operator in a namespace called pipelines as described in the documentation https://github.com/openshift/pipelines-tutorial/blob/master/install-operator.md and I deployed the tutorial not into pipeline-tutorial but inside pipelines namespaces !!!. the namespace pipeline-tutorial is referenced in several yaml file. I succeeded it by updating all yaml files with pipeline-tutorial. After this successful deployment I dropped all and I installed the operator in a separate pipelines namespace and I deployed the tutorial into a compelte separate namespace called pipelines-tutorial and it's working fine as expected.
build : push] Writing manifest to image destination
[build : push] Successfully pushed //image-registry.openshift-image-registry.svc:5000/pipelines-tutorial/spring-petclinic:latest@sha256:bbc7dfc26980c7257d20973cf5b9aea575b3b7f2bc9ad065d52347a262548cae
[build : push] Storing signatures
[build : image-digest-exporter-push-c8sqq] []
[build : nop] Build successful
[deploy : oc] deploymentconfig.apps.openshift.io/spring-petclinic rolled out
[deploy : nop] Build successful
Testing this tutorial on a OCP 4.1.2 version and after creating the PipelineRun, I'm checking the logs : tkn pr logs petclinic-deploy-pipelinerun-6d94f -f
any ideas ?
I tried to update the Task s2i-java-8 from
but same error . the OCP is a standard OCP 4.1.2 running on AWS (no advanced settings)