Description of problem: Migration failing with XDG_RUNTIME_DIR error in virt-v2v log Version-Release number of selected component (if applicable): CFME: 5.10.3.2.20190410215422_59d5d16 RHV: 4.3 v2v-conversion-host-ansible-1.12.1-4.el7ev.noarch v2v-conversion-host-wrapper-1.12.1-4.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install mentioned packages of conversion host and configure inventory file 2. Set conversion host (Since we had BZ1700457, I used workaround of rails commands to add host entry https://gist.github.com/fdupont-redhat/0661f6310e8ca0a1dab4b9016ea752e9) 3. Run migration (I used VDDK transformation method, I don't think this matters) Actual results: Migration failing with XDG_RUNTIME_DIR error in virt-v2v.log Expected results: Migration should pass. Additional info:
Fixed upstream by commit: 185d75aca9e75731a39de72ec68d398cac610952 wrapper: rhv: drop XDG_RUNTIME_DIR from environment (RHBZ#1700461)
Fixed in v2v-conversion-host-1.12.1-5.el7ev
Marking failedQA due to conversion hosts is not getting added which blocks end-to-end migration (BZ1696437). Checked against CFME 5.10.4.0.20190424160602_acb6009 and with v2v-conversion-host-wrapper-1.12.1-5.el7ev.noarch of recent RHV 4.3.3-5 compose.
It seems bug 1696437 is now fixed, please retest.
Checked with v2v-conversion-host-wrapper-1.12.1-5.el7ev.noarch of previous RHV 4.3.3-5 compose and migration worked after adding CFME's patches. No more XDG_RUNTIME_DIR error atm. Thanks a lot for fix.
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/RHBA-2019:1559