Bug 1466550

Summary:	[docs] Download link for hypervisor ISO in compatibility matrix page In RHEV 3.x
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ulhas Surse <usurse>
Component:	Documentation	Assignee:	rhev-docs <rhev-docs>
Status:	CLOSED DUPLICATE	QA Contact:	rhev-docs <rhev-docs>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.10	CC:	fgarciad, gveitmic, lsurette, mkalinin, rbalakri, srevivo, ykaul
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-30 21:09:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ulhas Surse 2017-06-30 01:19:04 UTC

Description of problem:
In host compatibility matrix, the version are confusing across RHEV versions.

9.2. Host Compatibility Matrix
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Installation_Guide/Host_Compatibility_Matrix.html

Vdsm versions of RHEL 7.2 in 3.5 image and 3.6 image are not same so if someone install 7.2 image of RHEV 3.5 considering that it is also compatible with the RHEV 3.6 version, the setup will fail.
  
Version-Release number of selected component (if applicable):
RHEVM 3.X

How reproducible:
Always


Actual results:
ISO versions are not forward compatible to vdsm version and so the table is misleading. 

Expected results:
Is it possible to include the ISO direct download link for respective versions in the table.

Additional info:

Comment 3 Marina Kalinin 2017-06-30 21:09:03 UTC

I suggest closing this bug as a duplicate of this bz#1466557, since the second is more detailed + we should not keep this table in the documentation but rather point to the life cycle page.

If someone disagrees, please reopen.

*** This bug has been marked as a duplicate of bug 1466557 ***