Bug 1996169

Summary: When "None" is selected as the target storage class in the web console, the setting is ignored and the default storage class is used
Product: Migration Toolkit for Containers Reporter: Erik Nelson <ernelson>
Component: UIAssignee: John Matthews <jmatthew>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: unspecified    
Version: 1.5.1CC: apinnick, ernelson, ibolton, prajoshi, rjohnson, sregidor, ssingla, whu, xjiang
Target Milestone: ---   
Target Release: 1.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1996125 Environment:
Last Closed: 2021-09-29 14:35:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version: 1.6.0
Embargoed:
Bug Depends On: 1996125    
Bug Blocks:    

Description Erik Nelson 2021-08-20 18:09:50 UTC 
+++ 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:
Comment 1 Erik Nelson 2021-08-23 16:43:06 UTC 
https://github.com/konveyor/mig-ui/pull/1277
Comment 5 ssingla 2021-08-30 11:15:53 UTC 
Bug is not seen in the latest build on verification and hence moving the status to verified.
Comment 7 errata-xmlrpc 2021-09-29 14:35:03 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.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