Bug 1899692

Summary:	[pvc-migrate] Source PVCs using storageclass annotation instead of spec.storageClass causes mapping to be ignored
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	General	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED WORKSFORME	QA Contact:	Xin jiang <xjiang>
Severity:	unspecified	Docs Contact:	Avital Pinnick <apinnick>
Priority:	unspecified
Version:	1.3.z	CC:	ernelson
Target Milestone:	---
Target Release:	---
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:	2021-04-08 02:38:41 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 Erik Nelson 2020-11-19 19:30:24 UTC

Description of problem:
Bug is against pvc-migrate project, not MTC proper. https://github.com/konveyor/pvc-migrate/issues/148

When running pvc-migrate, we have seen users with pvcs using storageclass annotations (a deprecated designation format) rather than spec.storageClass. This will cause the storageclass mapping to be ignored and pvcs on the target side will be provisioned using whatever the default provisioner is.

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

How reproducible:
Every time

Steps to Reproduce:
1. Create source workload using a pvc that has a storageclass designated via annotation rather than spec.storageClass

Actual results:
Target pvc will be created using the cluster default storageclass, or further breakage.

Expected results:
Target pvc should be created using the storageclass mapping setting

Comment 1 Erik Nelson 2021-04-08 02:38:41 UTC

Closing as stale