Description of problem: Pipelines failed to start with default namespace. Version-Release number of selected component (if applicable): 4.14 Deployed: OCP-4.14.0-ec.3 Deployed: CNV-v4.14.0.rhel9-1867 How reproducible: always Steps to Reproduce: 1.spawn a pipeline with win10 2. 3. Actual results: pipeline failed Expected results: pipeline succeed Additional info:
W/A to this problem is use custom namespace and create all tekton resources(tasks,pipelines) are available in custom namespace. 1. create a custom namespace. oc create ns test-tekton-pipeline 2. Make sure HCO is setup with below fields under spec. tektonPipelinesNamespace: test-tekton-pipeline tektonTasksNamespace: test-tekton-pipeline 3. save and wait for ssp to in "deployed" status. 4. Verify all windows pipeline exist under custom namespace and trigger pipeline from UI to make sure it works.
Test Env: Deployed: OCP-4.14.0-rc.2 Deployed: CNV-v4.14.0.rhel9-2094 Works with default namespace and ssp moved to deployed status.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6817