Executed the Rollback after performing Storage Class Conversion type migration on the target cluster. But the Rollback doesn’t complete and keeps running forever on “Cleanup Migrated” stage. Severity : High Version-Release number of selected component (if applicable): Source Cluster : 4.6 aws Target Cluster : 4.9 aws MTC 1.7.0 OADP 0.5.5 How reproducible: Always Steps to reproduce: 1. Deploy django application in the target cluster 2. Login to MTC UI and Create a migplan with Migration type “Storage Class Conversion” 3. Select ceph storage as target storage class and execute migration. 4. After the migration is successful, Again Perform a Rollback Actual result: The application pods references are not updated and PVC remains in “Terminating” state forever. Rollback keeps running forever. Expected result: The migrated PV/PVCs with new storage class should be removed and the references should be updated in the application pods.
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 (Migration Toolkit for Containers (MTC) 1.7.0 release advisory), 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/RHBA-2022:1043