Bug 1791012

Summary: [MIG-UI] NFS Move results in a warning
Product: Migration Toolkit for Containers Reporter: Sergio <sregidor>
Component: GeneralAssignee: Erik Nelson <ernelson>
Status: CLOSED NOTABUG QA Contact: Sergio <sregidor>
Severity: low Docs Contact: Avital Pinnick <apinnick>
Priority: low    
Version: 1.3.0CC: chezhang, ernelson, jmatthew, pvauter, rpattath, whu, xjiang
Target Milestone: ---   
Target Release: 1.4.z   
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: 2020-12-04 08:39:09 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 Sergio 2020-01-14 16:52:54 UTC
Description of problem:
Create a migration plan to move a nfs external volume (access RWO,ROX,RWX) to a cluster with no OCS4 installed results in a warning like:

move-nfs has been validated with warning condition(s). See warning message.
AccessMode for PVC in `persistentVolumes` [pv16] unavailable in chosen storage class


Version-Release number of selected component (if applicable):
CAM 1.1 osbs

CONTROLLER:
    image: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-controller-rhel8@sha256:b55c0c36333656a46e1d0500cf11cc8aa06e093d312e7c54f8e1075d4ab4c6c1

TARGET OCP:
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-01-11-070223   True        False         36h     Cluster version is 4.3.0-0.nightly-2020-01-11-070223

SOURCE OCP:
$ oc version
oc v3.11.126
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://
openshift v3.11.157
kubernetes v1.11.0+d4cacc0


How reproducible:
Always


Steps to Reproduce:

1. Create an application in source cluster with pvcs using external nfs volumes, for instance:

NAME         STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nginx-html   Bound     pv16      100Gi      RWO,ROX,RWX                   56m
nginx-logs   Bound     pv18      100Gi      RWO,ROX,RWX                   56m

2. Create a migration plan and select "Move" action to migrate the nfs pvcs


Actual results:
When the plan is created, a warning is displayed with a message like this:

move-nfs has been validated with warning condition(s). See warning message.
AccessMode for PVC in `persistentVolumes` [pv16] unavailable in chosen storage class


Expected results:
When "move" action is used, this kind of warnings should not happen.



Additional info:

As far as I see, in the background the MigPlan resource is created with default content while the user is selecting the information.

This default content is created with "copy" action and, hence, the warning. When the user clicks "Finish", is when the action is updated to "move", but the warning is still displayed to the user. This warning makes sense for "copy" action (the default value) but not for "move".

Comment 1 Erik Nelson 2020-01-16 00:36:56 UTC
We exhaustively discussed this and the root cause and determined this is not something we can fix correctly for the 1.1 release. There is a controller and UI issue logged to track this problem and the design we intend to implement for our next release:

https://github.com/fusor/mig-controller/issues/401
https://github.com/fusor/mig-ui/issues/654