Bug 1506262 - Provide ovirt-host package in 4.1
Summary: Provide ovirt-host package in 4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-hypervisor-ng
Version: 4.1.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.8
: ---
Assignee: Yuval Turgeman
QA Contact: dguo
URL:
Whiteboard:
Depends On: 1503124 1506258
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-25 14:02 UTC by Lukas Svaty
Modified: 2021-09-09 12:46 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of: 1506258
Environment:
Last Closed: 2017-12-12 09:24:45 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43457 0 None None None 2021-09-09 12:46:56 UTC
Red Hat Product Errata RHBA-2017:3431 0 normal SHIPPED_LIVE redhat-virtualization-host bug fix, and enhancement update for RHV 4.1.8 2017-12-12 14:17:28 UTC
oVirt gerrit 82875 0 None MERGED packaging: Adapt for 4.1 2020-05-01 22:51:47 UTC
oVirt gerrit 84510 0 ovirt-4.1 MERGED Adding ovirt-host requirement 2020-05-01 22:51:48 UTC

Comment 1 dguo 2017-12-01 09:46:47 UTC
Test versions:
rhvh-4.1-0.20171127.0+1
rhvm-4.2.0-0.5.master.el7
vdsm-4.19.40-1.el7ev.x86_64

Test steps:
1. Install rhvh-4.1.8
2. Check ovirt-host package
# rpm -q ovirt-host
3. Add rhvh-4.1.8 to compatibale 4.1 cluster on rhvm4.2

Actual results:
1. After step#2
[root@localhost ~]# rpm -q ovirt-host
ovirt-host-4.1.0-2.el7ev.noarch
2. After step#3, rhvh-4.1.8 can be added to a 4.1 cluster on rhvm4.2

Additional info:
1. The rhvh-4.1.8 also can be added to rhvm4.1

According to above result, changed bug status to verified

Comment 4 errata-xmlrpc 2017-12-12 09:24:45 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-2017:3431


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