+++ This bug was initially created as a clone of Bug #1996125 +++ Description of problem: When we select "None" as the destination storage class, the selection is ignored and the migration plan uses the default storage class instead. Version-Release number of selected component (if applicable): MTC 1.5.1 and MTC 1.6.0 How reproducible: Always Steps to Reproduce: 1. Deploy an application with a PVC oc new-project django oc new-app django-psql-persistent 2. Create a migration plan for this namespace 3. In the "Copy options" screen, select "None" as the destination storage class Actual results: The created migration plan will use the default storage class as the destination storage class instead of "None" as we selected when creating the migration plan. What we get in the migplan yaml information is this: selection: action: copy copyMethod: filesystem storageClass: gp2 Expected results: The migration plan should not use the default storage class, and no storage class should be used as the destination storage class. What we should get in the migplan yaml information is this: selection: action: copy copyMethod: filesystem Additional info:
https://github.com/konveyor/mig-ui/pull/1277
Bug is not seen in the latest build on verification and hence moving the status to verified.
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.6.0 security & bugfix 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-2021:3694