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:
The customize pipeline now allows to define sourceDiskImageName param https://github.com/kubevirt/ssp-operator/pull/550/files#diff-a8660ed0e74faf9517ab903a0c5a0e9fe4c5a0f1bf4415436350ebefec1ec08fR30
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.
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