Bug 1392998 - [Docs] [Installation] Information on rhev 3.5 support with Hypervisor RHEL 7.2 is missing from Red Hat Virtualization Life Cycle document.
Summary: [Docs] [Installation] Information on rhev 3.5 support with Hypervisor RHEL 7....
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.5.7
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 16:25 UTC by Koutuk Shukla
Modified: 2016-11-22 02:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 02:20:32 UTC
oVirt Team: Docs
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Koutuk Shukla 2016-11-08 16:25:01 UTC 
Description of problem:

Information on rhev 3.5 support with Hypervisor RHEL 7.2 is missing from Red Hat Virtualization Life Cycle document.
https://access.redhat.com/support/policy/updates/rhev

Version-Release number of selected component (if applicable):
rhev 3.5

Actual results: 
Below link states. Hypervisor RHEL 7.2 is supported only with rhev 3.6 and 4.0.
https://access.redhat.com/support/policy/updates/rhev

However rhev 3.5 also supports Hypervisor RHEL 7.2 per below installation document link.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Installation_Guide/Host_Compatibility_Matrix.html

Expected results:

Below link needs to be updated with the correct information.
https://access.redhat.com/support/policy/updates/rhev
Comment 1 Lucy Bopf 2016-11-22 02:20:32 UTC 
RHEL 7.2 support for RHEV 3.5 was confirmed in https://bugzilla.redhat.com/show_bug.cgi?id=1229358

I have updated the article accordingly: https://access.redhat.com/support/policy/updates/rhev
Note You need to log in before you can comment on or make changes to this bug.