Bug 1996125

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:	Sergio <sregidor>
Component:	UI	Assignee:	Ian <ibolton>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	unspecified
Version:	1.5.1	CC:	ernelson, ibolton, prajoshi, rjohnson, ssingla, whu, xjiang
Target Milestone:	---
Target Release:	1.5.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1996169 (view as bug list)		Environment:
Last Closed:	2021-08-31 08:10:13 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:	1.6.0
Embargoed:
Bug Depends On:
Bug Blocks:	1996169

Description Sergio 2021-08-20 15:48:16 UTC

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 4 Sergio 2021-08-26 14:31:40 UTC

Verified using
GCP 4.6 -> GCP 4.8. MTC 1.5.1

openshift-migration-legacy-rhel8-operator@sha256:a7062c6466b6f2467301de98bb78af45c4ec7fb75dfcf68b2ed0a0b354777336
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 6731c74dd154dcb40ace9d4876b77dc2610bcc717898be03ea33ad85a5078256
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: 8b29a1dd23200af0f2c7676f1cbf94d19fab0a3287aa101d79a9787b1bc07e88


After selecting "None" as the destination storage class, we got this data in the migplan resource:

      selection:
        action: copy
        copyMethod: filesystem
      storageClass: standard

And we got this warning in the migplan resource:

PV in `persistentVolumes` [pvc-5511622e-d77c-42fb-97c0-14b21eabf291] has no `Selected.StorageClass`. Make sure that the necessary static persistent volumes exist in the destination cluster.


We move the BZ to VERIFIED status.

Comment 8 errata-xmlrpc 2021-08-31 08:10:13 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.5.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-2021:3361