Bug 1899692 - [pvc-migrate] Source PVCs using storageclass annotation instead of spec.storageClass causes mapping to be ignored
Summary: [pvc-migrate] Source PVCs using storageclass annotation instead of spec.stora...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pranav Gaikwad
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-19 19:30 UTC by Erik Nelson
Modified: 2024-03-25 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: 2021-04-08 02:38:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.