Bug 2251676

Summary:	Advise Trident provisioner to use csi-clone
Product:	Container Native Virtualization (CNV)	Reporter:	Arnon Gilboa <agilboa>
Component:	Storage	Assignee:	Adam Litke <alitke>
Status:	CLOSED NOTABUG	QA Contact:	Natalie Gavrielov <ngavrilo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.14.0
Target Milestone:	---
Target Release:	4.14.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-27 08:08:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arnon Gilboa 2023-11-27 08:06:23 UTC

This bug was initially created as a copy of Bug #2247654

StorageProfiles ease the burden of selecting the optimal PVC parameters (AccessMode and VolumeMode) for known CSI provisioners. As we encounter new provisioners we should determine the correct values and update our internal table in CDI so that our customers will get a better out of the box experience. Having a correct storage profile can also make VM provisioning order of magnitude faster (CSI clone vs. default host-assisted clone). Several customer support cases have already arisen because the OCP certified provisioner had an empty or incorrect admin provided storage profile.

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

How reproducible:
100%

Steps to Reproduce:
Create DV with any Trident storage class (provisioner: csi.trident.netapp.io).

Actual results:
StorageProfile has no cloneType, therefore DV will use host-assisted clone.

Expected results:
StorageProfile has cloneStrategy: csi-clone

Additional info: