Bug 1672591

Summary:	[V2V] Update Conversion host dependecies and rebuild
Product:	Red Hat OpenStack	Reporter:	Marek Aufart <maufart>
Component:	ovirt-ansible-v2v-conversion-host	Assignee:	Marek Aufart <maufart>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	mariel, ohochman, rheslop, tvignaud
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-v2v-conversion-host-1.9.1-2.el7ev	Doc Type:	Bug Fix
Doc Text:	Previously, the `virt-v2v-wrapper` failed to detect Red Hat OpenStack volumes leading to migration failures. This was due to an update to the the v2v conversion host that changed the the `virt-v2v` output. After this fix, `virt-v2v-wrapper` can now detect Red Hat OpenStack volumes correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-18 13:04:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1668049
Bug Blocks:

Description Marek Aufart 2019-02-05 11:44:29 UTC

Description of problem: We need new build of V2V OSP Conversion host image (and ensure that the file with image is also included in RPM).


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Mikey Ariel 2019-02-20 12:44:23 UTC

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Comment 5 errata-xmlrpc 2019-03-18 13:04:09 UTC

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:0591