Bug 1394400 - RHEV-H 3.5 based RHEL 7 is not available for download
Summary: RHEV-H 3.5 based RHEL 7 is not available for download
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: releng
Version: 3.5.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Joey Boggs
QA Contact: Entitlement Bugs
URL:
Whiteboard: hosted-engine
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 21:02 UTC by Marina Kalinin
Modified: 2021-08-30 12:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-14 16:55:32 UTC
oVirt Team: Node
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43234 0 None None None 2021-08-30 12:26:17 UTC
Red Hat Knowledge Base (Solution) 2351141 0 None None None 2016-11-11 21:06:57 UTC

Description Marina Kalinin 2016-11-11 21:02:40 UTC
RHEV-H 3.5 based RHEL7 is necessary for upgrading hosted engine environments with RHEL6 hosts from 3.5 to 3.6. Specifically, it is required to have RHEVH based 7.2 with vdsm and ha packages from 3.5, ha packages 1.2.

Last known version to me that meets this criteria is :
 rhev-hypervisor7-7.2-20160219.0.el6ev
And it is not available any where on the portal.

IF you go to this link:
  https://access.redhat.com/downloads/content/150/ver=3.5/rhel---6/3.5/x86_64/product-software
there is only RHEVH based RHEL 6 available.

Impact:
customers cannot perform 3.5 to 3.6 HE upgrade.

Workaround:
# yumdownloader rhev-hypervisor7-7.2-20160219.0.el6ev
or download it from here:
http://ftp.redhat.com/pub/redhat/rhev-m/3.x/SRPMS/

I hope I opened on the correct component and it should not be on rhev-hypervisor. This issue needs to be addressed ASAP.

Comment 1 Fabian Deutsch 2016-11-12 19:48:23 UTC
RHEV-H 3.5 is el6 only - there are no el7 based builds (maybe a tech preview build tho).

el7 support is in RHEV-H 3.6 and later only.

There is also no direct upgrade path from el6 to el7 hosts.

The intended upgrade path is to replace el6 with el7 hosts using RHEV 3.6, then move to RHV 4, once all hosts have been migrated to el7.

Anything I am missing?

Comment 2 Yaniv Kaul 2016-11-13 07:23:48 UTC
(In reply to Fabian Deutsch from comment #1)
> RHEV-H 3.5 is el6 only - there are no el7 based builds (maybe a tech preview
> build tho).
> 
> el7 support is in RHEV-H 3.6 and later only.
> 
> There is also no direct upgrade path from el6 to el7 hosts.
> 
> The intended upgrade path is to replace el6 with el7 hosts using RHEV 3.6,
> then move to RHV 4, once all hosts have been migrated to el7.

How do they upgrade from 3.5 to 3.6, if there's no RHEVH 7.2 based hypervisor (I thought there was, btw - perhaps a confusion between RHEVH and RHVH NGN?)

> 
> Anything I am missing?

Comment 3 Fabian Deutsch 2016-11-13 10:31:30 UTC
Reinstallation of hosts was the only option to move from el6 to el7 - regardless of the version.

There is actually a bug tracking this migration path: bug 1290340.

Comment 4 Marina Kalinin 2016-11-14 14:35:20 UTC
There is no way to upgrade HE 3.5 to 3.6 without this specific RHEVH 3.5 based RHEL7.
It requires 1.2 ha packages to trigger upgrade of HA and import the HE SD into RHEV environment, which is happening during 1.2 to 1.3 ha packages update. 
IT is impossible to achieve any other simple way, since the channel that ships vdsm and ha packages for RHEL7 contains the current latest version (latest 3.6) and it is hard to manually ensure that all the exact 3.5 packages are pulled to the host when it is added as to HE setup. That's is why it was agreed that we need to use a locked version of packages, available on RHEV-H, to perform this upgrade.
For details, check HE upgrade flow:
https://access.redhat.com/solutions/2351141

Or, for example, errata for the last RHEV-H built that is needed for the process, but nowhere available for download:
https://rhn.redhat.com/errata/RHEA-2016-0312.html


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