Bug 1803747

Summary: RHHI-V deployment guide should point to latest RHV-RHGS docs
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: doc-Deploying_RHHIAssignee: Disha Walvekar <dwalveka>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.7CC: asriram, dwalveka, rhs-bugs
Target Milestone: ---   
Target Release: RHHI-V 1.7.z Async Update   
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: 2020-02-26 08:05:43 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:
Bug Depends On:    
Bug Blocks: 1804071    

Description SATHEESARAN 2020-02-17 11:02:28 UTC
Description of problem:
------------------------

Section '3.9. Existing Red Hat Gluster Storage configurations' 
Contains a link to RHGS 3.4 RHV-RHGS Guide

<snip>
refer to the traditional configuration documented in Configuring Red Hat Virtualization with Red Hat Gluster Storage. (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html/configuring_red_hat_virtualization_with_red_hat_gluster_storage/index) 
</snip>

This link should point to RHGS 3.5 based RHV-RHGS guide

Comment 4 SATHEESARAN 2020-02-24 09:14:07 UTC
(In reply to Disha Walvekar from comment #3)
> Hi Sas, 
> 
> Laura has already fixed this as part of the bug - BZ1805021
> 
> Link to this doc -
> https://access.redhat.com/documentation/en-us/
> red_hat_hyperconverged_infrastructure_for_virtualization/1.7/html-single/
> deploying_red_hat_hyperconverged_infrastructure_for_virtualization//
> index?lb_target=stage#rhhi-limits-existing-gluster
> 
> Thank you.

The reference now takes to RHV-RHGS guide based on RHGS 3.5

Comment 5 SATHEESARAN 2020-02-24 09:14:56 UTC
Based on comment4 moving this bug to verified