DescriptionSandro Bonazzola
2017-10-18 07:05:29 UTC
+++ This bug was initially created as a clone of Bug #1477632 +++
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:
--- Additional comment from Marina on 2017-08-14 10:31:46 EDT ---
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
--- Additional comment from Yaniv Lavi (Dary) on 2017-08-28 05:44:46 EDT ---
Any updates?
--- Additional comment from Simone Tiraboschi on 2017-09-27 14:13:09 EDT ---
(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.
--- Additional comment from Douglas Schilling Landgraf on 2017-10-17 11:37:44 EDT ---