Bug 1600012

Summary: [RFE] Make ovirt-ansible-v2v-conversion-host RPM available in OSP repos
Product: Red Hat OpenStack Reporter: Marek Aufart <maufart>
Component: ovirt-ansible-v2v-conversion-hostAssignee: Marek Aufart <maufart>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: apannu, markmc, maufart, mburns, ohochman, srevivo, tgolembi
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-ansible-v2v-conversion-host-1.6.0-1.el7ev Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:42:57 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:    
Bug Blocks: 1595944    

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