OpenShift Virtualization - VM Import conversion POD disk

Solution Verified - Updated

Environment

OpenShift 4.4
OpenShift Virtualization 2.3
NFS storage

Issue

In OpenShift Virtualization 2.3, the VM import feature for migrating a VM from VMware to OpenShift Virtualization will fail if an NFS backed storage class is used for the 2GB disk that is attached to the conversion POD.

Resolution

To resolve this issue, please configure a hostPath volume for your OpenShift deployment. This storage class will then be selected to be used for the conversion POD when importing a VM from VMware.

Please refer to: This page is not included, but the link has been rewritten to point to the nearest parent document.Red Hat OpenShift Container Platform, configuring persistent storage on how to configure hostPath storage.

Root Cause

The root cause of the issue is due to virt-v2v missing support for NFS storage when performing a VM conversion. Reference BZ: This content is not included.virt-v2v does not work when /var/tmp is mounted on NFS

Diagnostic Steps

When importing a VM from VMware to OpenShift Virtualization, the migration fails and the following error will appear in the container logs:
libguestfs: error: security: cached appliance /var/tmp/.guestfs-0 is not owned by UID 0

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.