Bug 2170699

Summary: Tekton: pipelineref windows10-customize should provide parameter for dv name
Product: Container Native Virtualization (CNV) Reporter: Geetika Kapoor <gkapoor>
Component: InfrastructureAssignee: Karel Šimon <ksimon>
Status: VERIFIED --- QA Contact: Geetika Kapoor <gkapoor>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.12.1   
Target Milestone: ---   
Target Release: 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kubevirt-ssp-operator-rhel9-container-v4.14.0-69 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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-02-16 23:49:52 UTC
Description of problem:

windows10-installer currently provides a way to configure own dv name. While windows10-customize lack this feature. It looks for a hard coded win10 dv name and pipelines failed if not found.

Version-Release number of selected component (if applicable):

4.12.1
How reproducible:
always

Steps to Reproduce:
1.Create a test dv. Example: win10-test1
2. Now trigger pipelinerun for windows10-customize
3. pipeline will fail while vmi creation and later delete and cleanup won't run.

Actual results:

Pipeline is not running and failing with non default dv name
Expected results:

pipeline should let user configure their own dv name and pipeline should be green 
Additional info:

Comment 2 Karel Šimon 2023-06-20 07:02:00 UTC
The customize pipeline now allows to define sourceDiskImageName param https://github.com/kubevirt/ssp-operator/pull/550/files#diff-a8660ed0e74faf9517ab903a0c5a0e9fe4c5a0f1bf4415436350ebefec1ec08fR30

Comment 3 Geetika Kapoor 2023-07-31 13:09:00 UTC
Test Env: 4.14

Test steps:
1. Validate there is a way to provide custom dv namespace and "baseDvNamespace" parameter solved that purpose.
2. Try and test pipelines with these params and it worked.