Bug 2237916

Summary:	Pipelines failed when triggered with default namespace openshift-cnv
Product:	Container Native Virtualization (CNV)	Reporter:	Geetika Kapoor <gkapoor>
Component:	Infrastructure	Assignee:	Karel Šimon <ksimon>
Status:	CLOSED ERRATA	QA Contact:	Geetika Kapoor <gkapoor>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.14.0	CC:	ksimon, ycui
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kubevirt-ssp-operator-rhel9-container-v4.14.0-108	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 14:06:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Geetika Kapoor 2023-09-07 17:18:59 UTC

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:

Comment 1 Geetika Kapoor 2023-09-11 11:40:04 UTC

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.

Comment 2 Geetika Kapoor 2023-09-27 11:33:24 UTC

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.

Comment 4 errata-xmlrpc 2023-11-08 14:06:16 UTC

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