Bug 2072684

Summary:	Storage Conversion: PersistentVolumeClaimTemplates in StatefulSets are not updated automatically after migration
Product:	Migration Toolkit for Containers	Reporter:	Pranav Gaikwad <pgaikwad>
Component:	Controller	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Prasad Joshi <prajoshi>
Severity:	high	Docs Contact:	Richard Hoch <rhoch>
Priority:	high
Version:	1.7.0	CC:	prajoshi, rjohnson
Target Milestone:	---
Target Release:	1.7.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:	2022-05-05 13:50:07 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 Pranav Gaikwad 2022-04-06 18:41:31 UTC

Description of problem:
volumeClaimTemplates in StatefulSet resources are not updated to point to new PVC resources after a storage conversion migration.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a storage conversion plan for a namespace that has statefulset resources in it
2. Run a stage + cutover migration

Actual results:
The volumeClaimTemplates in StatefulSets are not updated automatically after migration

Expected results:
The volumeClaimTemplates in StatefulSets should be updated automatically after migration


Additional info:

Comment 6 Prasad Joshi 2022-04-26 12:28:06 UTC

Verified with MTC 1.7.0(prestage)

metadata_nvr: openshift-migration-operator-metadata-container-v1.7.1-10

Source cluster: AWS 4.5 
Target cluster: AWS 4.10

The volumeClaimTemplates in Statefulsets are getting updated after performing migrations.

$ oc get pods -o yaml

    volumes:
    - name: data-new
      persistentVolumeClaim:
        claimName: data-new-redis-ss-1

$ oc get pvc
NAME                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS            AGE
data-new-redis-ss-0   Bound    pvc-1fc16b69-cfc9-428f-94cd-92f9dd0dfb95   100Mi      RWO            odf-operator-ceph-rbd   10m
data-new-redis-ss-1   Bound    pvc-03cf8cfd-612e-4e3f-8a77-5ec00678dcbb   100Mi      RWO            odf-operator-ceph-rbd   10m
data-redis-ss-0       Bound    pvc-b09a7752-849c-4278-985c-dcebf70ac060   1Gi        RWO            standard                30m
data-redis-ss-1       Bound    pvc-2a383625-7360-4bd2-97a1-422b570ef8f9   1Gi        RWO            standard                29m


Moving this to verified status.

Comment 8 errata-xmlrpc 2022-05-05 13:50:07 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Migration Toolkit for Containers (MTC) 1.7.1 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:1734