Bug 1600012 - [RFE] Make ovirt-ansible-v2v-conversion-host RPM available in OSP repos
Summary: [RFE] Make ovirt-ansible-v2v-conversion-host RPM available in OSP repos
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: ovirt-ansible-v2v-conversion-host
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Marek Aufart
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1595944
TreeView+ depends on / blocked
 
Reported: 2018-07-11 08:26 UTC by Marek Aufart
Modified: 2019-10-22 06:02 UTC (History)
7 users (show)

Fixed In Version: ovirt-ansible-v2v-conversion-host-1.6.0-1.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:42:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0046 0 None None None 2019-01-11 11:43:18 UTC

Description Marek Aufart 2018-07-11 08:26:40 UTC
Description of problem: In order to have working V2V, Conversion VM is needed ( BZ1595944). On the VM, there should be installed the package actually placed in oVirt/RHV product. We need make "ovirt-ansible-v2v-conversion-host" RPM and its dependencies available in OpenStack repos.


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


How reproducible:


Steps to Reproduce:
1. # yum install ovirt-ansible-v2v-conversion-host
2.
3.

Actual results: Package ovirt-ansible-v2v-conversion-host is not available in OpenStack repo channel.


Expected results: Package ovirt-ansible-v2v-conversion-host should be possible to install from OpenStack repos.


Additional info: This should be part of [1] https://bugzilla.redhat.com/show_bug.cgi?id=1595944#c4

Comment 16 errata-xmlrpc 2019-01-11 11:42:57 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/RHEA-2019:0046


Note You need to log in before you can comment on or make changes to this bug.