Description of problem: On a OCP cluster with storage "standard" - "kubernetes.io/cinder" set as the default storage, creating a migration plan, for a single RHEL7 VM, with storage mapping that maps to a non default storage, "nfs". After starting the plan, there is a trial to bound PVC to "standard" storage, and not to "nfs" as expected. the VM import remains "pending" forever. If changing the default storage to nfs, for a migration plan with destination storage nfs, the PVC is bound to nfs, and the migration plan ends successfully Version-Release number of selected component (if applicable): MTV 2.0.0-15 CNV-2.6.0 (Currently not able to use CNV-2.6.1 since of PSI down issue)
How is the mapping created? API or UI? Can you please share the YAML (oc get -o yaml) for the plan and mappings?
The mappings were created from UI.
Created attachment 1771616 [details] plan yaml
Created attachment 1771617 [details] storage mapping yaml
Created attachment 1771618 [details] Network mapping yaml
Created attachment 1771621 [details] dv yaml
Created attachment 1771622 [details] cdi deployment log
https://github.com/konveyor/forklift-controller/pull/215
The fix should be part of build 2.0.0-17 / iib:66911.
Apparently not in build 2.0.0-17. Moving back to MODIFIED.
The fix should be part of MTV 2.0.0-18 / iib:68063.
verified MTV 2.0.0-20 (iib:69034)
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 (MTV 2.0.0 images), 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/RHEA-2021:2381