Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1477632

Summary: Remove the need for a stepped upgrade between 3.5 to 3.6 with HE and RHEV-H
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Lavi <ylavi>
Component: ovirt-engineAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED ERRATA QA Contact: Nikolai Sednev <nsednev>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.10CC: apinnick, cshao, huzhao, irosenzw, jbelka, lsurette, mavital, mkalinin, nsednev, rbalakri, rbarry, Rhev-m-bugs, sbonazzo, srevivo, stirabos, ycui, ykaul, yzhao
Target Milestone: ovirt-3.6.z-asyncKeywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-3.6.12.3 Doc Type: Enhancement
Doc Text:
Upgrading a Red Hat Enterprise Virtualization 3.5 self-hosted engine environment, running on RHEL 6 or RHEV-H 6 hosts, to Red Hat Enterprise Virtualization 3.6, running on Next Generation RHVH or RHEL 7 hosts, has been greatly simplified
Story Points: ---
Clone Of:
: 1503446 (view as bug list) Environment:
Last Closed: 2018-02-07 14:10:48 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:
Bug Depends On:    
Bug Blocks: 1488891, 1489925, 1503445, 1503446, 1529957    

Description Yaniv Lavi 2017-08-02 13:52:18 UTC
Description of problem:
We currently recommend a stepped upgrade from 3.5 to 3.6 for HE.
As we now support 3.6 NGN for upgrade flow and CLI is supported on this hypervisor, CEE would like to have a simpler upgrade method that will not require a stepped upgrade.
I suggest providing steps to copy existing answer file from RHEV-H el6 3.5 to next generation RHV-H el7 3.6 and change the answer to make the setup think it is an upgrade.

Can you provide steps for this? 

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

How reproducible:
100%

Steps to Reproduce:
1. Upgrade RHV 3.5 to 3.6 with HE and RHEV-H/RHEL-H el6.
2. 
3.

Actual results:
You need to step the HE cluster upgrade with RHEV-H 3.5 el7.

Expected results:
Reinstall to next generation RHV-H 3.6 el7 or RHEL-H 3.6 el7 directly and have steps to trigger upgrade of HE.

Additional info:

Comment 1 Marina Kalinin 2017-08-14 14:31:46 UTC
Summary:
skipping 3.5 el6 -> 3.5 el7 -> 3.6 el7 ->3.6 el7 ngn 
going    3.5 el6 -> 3.6 el7 ngn


Just remember, the main reason for this 3.5 el7 -> 3.6 el7 was to trigger autoimport of HE SD, as per this solution:
https://access.redhat.com/solutions/2351141

Comment 2 Yaniv Lavi 2017-08-28 09:44:46 UTC
Any updates?

Comment 3 Simone Tiraboschi 2017-09-27 18:13:09 UTC
(In reply to Yaniv Lavi (Dary) from comment #2)
> Any updates?

https://docs.google.com/document/d/1aly0DoaKf1API1jIWY4p8Rwax9CLTMokXBWM9hQt2RY/edit#heading=h.dn56zw88plel

Maybe we could ship an helper script or a set of ansible playbooks to make it even easier.

Comment 4 Douglas Schilling Landgraf 2017-10-17 15:37:44 UTC
*** Bug 1489925 has been marked as a duplicate of this bug. ***

Comment 5 Yaniv Lavi 2017-10-18 08:48:24 UTC
This helper script need to be updated in the KBase, but doesn't require a backport to 3.6.z codebase.

Comment 6 Yaniv Lavi 2017-10-18 08:49:58 UTC
(In reply to Yaniv Lavi (Dary) from comment #5)
Correction:
> This helper script for this process needs to be updated in the documentation and should be included in the 3.6.z code base.

Comment 7 RHV bug bot 2017-12-31 11:42:12 UTC
*** Bug 1503446 has been marked as a duplicate of this bug. ***

Comment 18 Nikolai Sednev 2018-02-07 13:05:40 UTC
Worked for me with RHVH-3.6-20180130.0-RHVH-x86_64-dvd1.iso.
I've followed the https://access.redhat.com/documentation/en-us/red_hat_enterprise_virtualization/3.6/html-single/self-hosted_engine_guide/index#Upgrading_a_RHEL7_Self-Hosted_Engine section 6.3 for upgrading from 3.5 pair of RHEL6.9 to PAir of 3.6RHEVH NGNs.

Comment 21 errata-xmlrpc 2018-02-07 14:10:48 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-2018:0284

Comment 22 Franta Kust 2019-05-16 12:54:45 UTC
BZ<2>Jira re-sync