This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2225227 - Tekton: Consistent behavior in bios & efi pipelines for dv creation
Summary: Tekton: Consistent behavior in bios & efi pipelines for dv creation
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dominik Holler
QA Contact: Geetika Kapoor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-24 16:29 UTC by Geetika Kapoor
Modified: 2023-09-22 17:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-02 11:52:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-31319 0 None None None 2023-08-02 11:52:18 UTC

Description Geetika Kapoor 2023-07-24 16:29:27 UTC 
Description of problem:
or windows 10 pipeline, default dv namespace is openshift-virtualization-os-images and for windows 11,2022 it is openshift-cnv(even when we don't make any changes in default parameters.

$ oc get dv -A| grep win
openshift-cnv                        win11-z5dvj                     ImportInProgress   N/A        2          3m4s
openshift-cnv                        windows-efi-root-disk-qzrss     Succeeded          100.0%                3m3s
openshift-virtualization-os-images   win10                           Succeeded          100.0%                59m
openshift-virtualization-os-images   win10-test                      Succeeded          100.0%                33m
openshift-virtualization-os-images   windows-bios-installer-cd-rom   ImportInProgress   N/A        9          33m


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

How reproducible:

always
Steps to Reproduce:
1.Trigger a pipeline win10(bios) and win11(efi) with iso images and without making any change in other parameters.
2.
3.

Actual results:


Expected results:
expected consistent behavior

Additional info:
Comment 1 Karel Šimon 2023-08-02 10:49:17 UTC 
Both pipelines have the same result namespace for datavolumes. What is different is in which namespace the VM is running. Bios pipeline runs vm in the result namespace => this saves about 5-20 minutes of pipelineRun (depends on storageClass), because pipeline does not have to copy disk from one namespace to result namespace. Efi pipeline can't do that, because taskRun pod is mounting PVC for modification and pod can't mount PVC from different namespace.
Note You need to log in before you can comment on or make changes to this bug.