-
Bug
-
Resolution: Done
-
Undefined
-
2.6.4
-
None
-
None
-
False
-
None
-
False
-
-
-
Moderate
Description of problem:
The VM on VMWare running RHEL 8.9 has SELinux disabled and is failing to do a cold migration to a remote cluster
Version-Release number of selected component (if applicable):
MTV 2.6.4
How reproducible:
Steps to Reproduce: * Create the local provider as a remote provider, meaning to include the URL and other credentials to access the local cluster
- Create a VMWare provider
- VM must be running RHEL with SELinux disabled
- Create a migration plan
Actual results:
The conversion pod will fail with an SELinux error:
commandrvf: stdout=n stderr=y flags=0x0^M commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -m -r /sysroot -v /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/^M Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.^M setfiles: Could not set context for /sysroot/etc/issue.net: Operation not permitted^M guestfsd: error: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.^M setfiles: Could not set context for /sysroot/etc/issue.net: Operation not permitted^M libguestfs: trace: v2v: selinux_relabel = -1 (error)virt-v2v: error: libguestfs error: selinux_relabel: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.setfiles: Could not set context for /sysroot/etc/issue.net: Operation not permitted rm -rf '/var/tmp/null.HOvijA' libguestfs: trace: v2v: close libguestfs: closing guestfs handle 0x55a3cf159020 (state 2) libguestfs: trace: v2v: internal_autosync
Expected results:
To do a cold migration using a remote cluster and without needing SELinux enabled
Additional info:
Workaround was to create the same local provider and not include the URL or other credentials