Bug 1700461
Summary: | [v2v][RHV][Conversion] Migration failing with XDG_RUNTIME_DIR error in virt-v2v log | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yadnyawalk Tale <ytale> |
Component: | v2v-conversion-host | Assignee: | Tomáš Golembiovský <tgolembi> |
Status: | CLOSED ERRATA | QA Contact: | Yadnyawalk Tale <ytale> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | fdupont, michal.skrivanek, mtessun, rbarry, rdlugyhe, smallamp, tgolembi |
Target Milestone: | ovirt-4.3.5 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | v2v | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, migration failed with an XDG_RUNTIME_DIR error in the virt-v2v log. The current release fixes this error by dropping XDG_RUNTIME_DIR from the environment.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-20 14:47:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1696437 | ||
Bug Blocks: |
Description
Yadnyawalk Tale
2019-04-16 15:40:25 UTC
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 |