Steps to Reproduce:
1. Have a kubevirt-storage-class-defaults config map which contains "volumeMode: Block" configured for a storage class X
2. Go to the new VM dialog and try to import a VM
3. In the storage section, pick X as a storage class for any or all of the disks
4. Submit the dialog
The conversion pod will never start because it fails to mount the PVCs
The conversion succeeds
The problem is, that if the volume mode is Block, pvc should be mounted using volumeDevices and not volumeMounts
I have modified entrypoint script to handle the block devices. The change is here:
It requires corresponding change in the pod definition where the disks should be removed from `volumeMounts` section and included in `volumeDevices` section like this:
- name: hdd1
The device path is important and must conform to the name /dev/v2v-diskX where X is a number. This is how the entrypoint will find them during execution.
UI patch: https://github.com/kubevirt/web-ui-components/pull/557
Configuration of the temporary disk still needs to be resolved, discussion in progress within the PR.
PR merged and tested here: https://github.com/kubevirt/web-ui-components/pull/565
If it merged it has to move to "Modified,
And then I think it should automatically move to ON-QE once the target DS build (2.1.1) is delivered to QE.
Once we get the build with the fix will validate it.
This was actually supposed to be moved to on_qa. Fixing it now
please add 'fixed in version'
Merged Nov 21st to openshift/console 4.2 branch, so 4.2.0-0.nightly-2019-11-27-102509 build should contain.
Verified on Openshift 4.3/CNV 2.2.0-10:
With configmap set with volumeMode: Block (see configmap below),
managed to run Import VM several times successfully.
$ oc edit configmap kubevirt-storage-class-defaults -n openshift-cnv
volumeMode: Block <==== Block is configured
- apiVersion: hco.kubevirt.io/v1alpha1
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.