Bug 2188629 - Storage class conversion: Mig Plan results in error when a namespace contains a statefulset that uses a volume which is not created via a StatefulSet volume template
Summary: Storage class conversion: Mig Plan results in error when a namespace contains...
Keywords:
Status: NEW
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.8.0
Assignee: John Matthews
QA Contact: ssingla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-21 12:49 UTC by Pranav Gaikwad
Modified: 2023-07-03 02:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pranav Gaikwad 2023-04-21 12:49:33 UTC 
Description of problem:
Statefulsets can use volumes in two ways. First, it can create a volume it needs dynamically via spec.volumeClaimTemplates field. Second, it can use a normal volume not created by the statefulset itself via spec.volumes field. MTC fails to recognize volumes used by statefulsets which are under spec.volumes but not in spec.volumeClaimTemplates.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a PVC in a namespace.
2. Create a StatefulSet in the namespace and add the PVC in spec.volumes field just like you would add in a Pod spec.
3. Create MigPlan for that namespace.

Actual results:
MigPlan fails and generates an error about PVC name.

Expected results:
MigPlan shouldn't generate the error.

Additional info:
Note You need to log in before you can comment on or make changes to this bug.