Red Hat Bugzilla – Bug 1477632
Remove the need for a stepped upgrade between 3.5 to 3.6 with HE and RHEV-H
Last modified: 2018-02-07 09:10:48 EST
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):
Steps to Reproduce:
1. Upgrade RHV 3.5 to 3.6 with HE and RHEV-H/RHEL-H el6.
You need to step the HE cluster upgrade with RHEV-H 3.5 el7.
Reinstall to next generation RHV-H 3.6 el7 or RHEL-H 3.6 el7 directly and have steps to trigger upgrade of HE.
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:
(In reply to Yaniv Lavi (Dary) from comment #2)
> Any updates?
Maybe we could ship an helper script or a set of ansible playbooks to make it even easier.
*** Bug 1489925 has been marked as a duplicate of this bug. ***
This helper script need to be updated in the KBase, but doesn't require a backport to 3.6.z codebase.
(In reply to Yaniv Lavi (Dary) from comment #5)
> This helper script for this process needs to be updated in the documentation and should be included in the 3.6.z code base.
*** Bug 1503446 has been marked as a duplicate of this bug. ***
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.
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.