Bug 1887482 - [v2v][VM import from VMware to CNV] VM import with missing vddk-init-image is resulted with unclear error
Summary: [v2v][VM import from VMware to CNV] VM import with missing vddk-init-image is...
Keywords:
Status: CLOSED DUPLICATE of bug 1897891
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Tomas Jelinek
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-12 15:27 UTC by Ilanit Stein
Modified: 2020-12-16 12:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-16 12:21:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ilanit Stein 2020-10-12 15:27:16 UTC
Description of problem:
When importing from VMware to CNV in case the vddk init image is missing,
there is a warning in the VM import wizard page:

"Danger alert:Image configuration missing
The following images are missing in a v2v-vmware ConfigMap: vddk-init-image. Please see documentation for more information."

If this warning is ignored and VM import is run anyway,
it will immediately fail:
 
"Error creating virtual machine.
Error "Required value" for field "spec.initContainers[0].image".
Pod kubevirt-v2v-conversion-rhel8template- failed to create"

This last error message do not indicate at all that the problem is that vddk-init-image is missing.
 
Version-Release number of selected component (if applicable):
OCP-4.6/CNV-2.5

How reproducible:
100%

Expected results:
The error in case of VM import with no vddk-init-image should indicate that.

Additional info:
What's displayed when opening the 
"Pod kubevirt-v2v-conversion-rhel8template- failed to create"

{
 "kind": "Pod",
 "apiVersion": "v1",
 "metadata": {
  "generateName": "kubevirt-v2v-conversion-rhel8template-",
  "namespace": "default"
 },
 "spec": {
  "restartPolicy": "Never",
  "serviceAccountName": "kubevirt-v2v-conversion-22z27",
  "initContainers": [
   {
    "name": "vddk-init",
    "volumeMounts": [
     {
      "name": "volume-vddk",
      "mountPath": "/opt/vmware-vix-disklib-distrib"
     }
    ]
   }
  ],
  "containers": [
   {
    "name": "kubevirt-v2v-conversion",
    "imagePullPolicy": "IfNotPresent",
    "image": "registry.redhat.io/container-native-virtualization/kubevirt-v2v-conversion@sha256:3f713f9db2bc69b0e01ca3843d1d1170adf5864a25860e7f9ec53ea3a12153dc",
    "securityContext": {
     "privileged": true
    },
    "volumeMounts": [
     {
      "name": "configuration",
      "mountPath": "/data/input"
     },
     {
      "name": "kvm",
      "mountPath": "/dev/kvm"
     },
     {
      "name": "volume-vddk",
      "mountPath": "/opt/vmware-vix-disklib-distrib"
     },
     {
      "name": "v2v-conversion-temp",
      "mountPath": "/var/tmp"
     },
     {
      "name": "harddisk1",
      "mountPath": "/data/vm/disk1"
     }
    ],
    "volumeDevices": []
   }
  ],
  "volumes": [
   {
    "name": "configuration",
    "secret": {
     "secretName": "kubevirt-v2v-conversion-gb9bb"
    }
   },
   {
    "name": "kvm",
    "hostPath": {
     "path": "/dev/kvm"
    }
   },
   {
    "name": "volume-vddk",
    "emptyDir": {}
   },
   {
    "name": "v2v-conversion-temp",
    "emptyDir": {}
   },
   {
    "name": "harddisk1",
    "persistentVolumeClaim": {
     "claimName": "harddisk1-k2gm5"
    }
   }
  ]
 }
}

Comment 1 Tomas Jelinek 2020-10-13 07:52:26 UTC
The main issue is I'd say that once you have the warning the wizard will let you continue. I think it should stop you since it is clear the import will fail

Comment 2 Filip Krepinsky 2020-10-13 14:16:52 UTC
agree, we should not allow the wizard to proceed

Comment 3 Yaacov Zamir 2020-12-16 12:13:39 UTC
*** Bug 1884250 has been marked as a duplicate of this bug. ***

Comment 4 Yaacov Zamir 2020-12-16 12:21:06 UTC

*** This bug has been marked as a duplicate of bug 1897891 ***


Note You need to log in before you can comment on or make changes to this bug.