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".
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