Bug 1251722

Summary: Test that upgrade of el6 host to el7 works as expected.
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Lavi <ylavi>
Component: ovirt-engineAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: medium Docs Contact:
Priority: high    
Version: 3.6.0CC: bazulay, gklein, lsurette, owwang, pstehlik, rbalakri, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: TestOnly
Target Release: 3.6.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 21:11:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yaniv Lavi 2015-08-09 08:11:45 UTC 
Description of problem:
It is supported to upgrade server from el6 to el7.
We need to make sure it will work as expected when these are hosts in engine.
Please open bug as needed and block this one.
Comment 1 Yaniv Lavi 2015-09-03 10:45:38 UTC 
This is the solution to be used:
https://access.redhat.com/solutions/637583
Comment 3 Sandro Bonazzola 2016-01-19 14:52:10 UTC 
Haoxing Wang any reason for changing component?
Issue here is that we need to be sure that a EL6 node host can be updated to EL7.
As a special case, the host may be in Hosted Engine cluster.
Comment 4 Yaniv Lavi 2016-01-19 16:48:59 UTC 
(In reply to Sandro Bonazzola from comment #3)
> Haoxing Wang any reason for changing component?
> Issue here is that we need to be sure that a EL6 node host can be updated to
> EL7.
> As a special case, the host may be in Hosted Engine cluster.

Component changed due to collapsing of components to match upstream products.
ovirt-engine-setup is not a valid component any more.
Comment 5 Jiri Belka 2016-01-21 17:01:22 UTC 
ok,

vdsm-4.16.32-1.el6ev.x86_64 -> vdsm-4.17.18-0.el7ev.noarch

3.5 dc/3.5 cluster on 3.6.2-10 env -> 3.6 dc/3.6 cluster on 3.6.2-10 env
Comment 7 errata-xmlrpc 2016-03-09 21:11: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://rhn.redhat.com/errata/RHEA-2016-0376.html