Description of problem: Migration fails due to conversion pod uses incorrect path to the block device Version-Release number of selected component (if applicable): CNV 2.2.0-10 How reproducible: 100% Steps to Reproduce: 1. Start migration 2. Wait until it will fail 3. Observe logs of conversion pod Actual results: Migration fails Expected results: Migration should succeed Additional info:
Recent change in web UI modified the path at which are the block devices attached to the POD. Instead of fixing this in UI we opted for a quicker patch in the container.
Verification is blocked by: Bug 1784727 - [v2v] Import VM: UI becomes blank when picking a VM from VMware VMs list
Bug 1784727 mentioned in comment #3 is resolved on Openshift console version: 4.3.0-0.nightly-2019-12-19-050538. CNV -2.2.0-10 Migration of a RHEL7 VM worked just fine on: CNV -2.2.0-10 This is the conversion image denined in configMap: $ oc -n openshift-cnv edit cm v2v-vmware ... v2v-conversion-image: registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-kubevirt-v2v-conversion:v2.2.0-8 ...
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