Description of problem: When importing a VM to an env which does not support RWM/filesystem for storage, the import will never be initiated. The consequence, if you only have local or ceph storage in your env (e.g. RHHI.next env), you will not be able to use the v2v feature at all.
https://github.com/openshift/console/pull/2764
Since the v2v has been removed from 2.1.0, retargeting bugs to 2.1.1 to make sure they will be verified on the right version.
How to verify (Tomas Jelinek): best way would probably be to modify the "kubevirt-storage-class-defaults" storage class from openshift-cnv namespace and modify the value for the storage class you are using in a way which does not work. And than try to import and it should fail. Than fix it and try to import and it should pass. This way you should know that the wizard respects the configuration in kubevirt-storage-class-defaults. # oc -n openshift-cnv edit cm kubevirt-storage-class-defaults apiVersion: v1 data: accessMode: ReadWriteMany -> ReadWriteOnce local-sc.accessMode: ReadWriteOnce VM import failed (error_screenshot.png attached). Then returned it back to ReadWriteMany, and for the same VM import worked fine.
Created attachment 1645546 [details] error_screenshot.png
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, 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-2020:0307