Bug 1598064

Summary: [DOC]The RHHI for virt documentation includes wrong RHV version.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Mugdha Soni <musoni>
Component: doc-Deploying_RHHIAssignee: storage-doc
Status: CLOSED DUPLICATE QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhhiv-1.5CC: asriram, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-16 07:11:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot where RHV 4.1.8 is mentioned. none

Description Mugdha Soni 2018-07-04 09:09:39 UTC 
Created attachment 1456437 [details]
Screenshot where RHV 4.1.8  is mentioned.

Description of problem:
----------------------------------
The document mentioned in additional info  says that RHHI for Virtualization is deployed across three physical machines to create a discrete cluster or pod using Red Hat Gluster Storage 3.3.1 and Red Hat Virtualization 4.1.8.Where as for RHHI 2.0 RHV 4.2 is used.The same is also mentioned in following sections :-

(1)Operating System
(2)Architecture
(3)Install Hosts

How reproducible:
----------------------------------
Everytime

Steps to Reproduce:
---------------------------------
Link to document is "https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/2.0/html-single/deploying_red_hat_hyperconverged_infrastructure_for_virtualization/#verify_your_deployment".

Actual results:
--------------------------------
It is mentioned that RHV 4.1.8 is supported with RHHI 2.0.

Expected results:
---------------------------------
RHV 4.2 is supported with RHHI 2.0
Comment 1 Laura Bailey 2018-08-16 07:11:10 UTC 

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