Bug 1691791

Summary: Add the information on deployment procedure, when HE deployment fails
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: doc-Deploying_RHHIAssignee: Laura Bailey <lbailey>
Status: CLOSED CURRENTRELEASE QA Contact: bipin <bshetty>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.6CC: asriram, lbailey, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: RHHI-V 1.6.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: 2019-08-05 06:17:17 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: 1723361    

Description SATHEESARAN 2019-03-22 14:19:05 UTC 
Description of problem:
-----------------------
When HE deployment fails, users should proceed with 'Hyperconverged' deployment -> 'Use existing configuration' method to start with the HE deployment. In this case, existing gluster volumes and configurations will be used.

Most of the times, users misunderstand and choose 'Hosted Engine' deployment instead of 'Hyperconverged' -> use existing configuration, and that will lead to more problems like gluster service not enabled on the cluster.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI-V 1.6 deployment docs


Actual results:
---------------
No info about how to proceed with deployment, when HE deployment fails due to manual errors - for example incorrect gateway, IP, FQDN, etc

Expected results:
-----------------
Need to support doc that explains user to use the existing configuration via: 'Hyperconverged Deployment' -> 'Use Existing Configuration' in the cockpit deployment wizard.


Additional info:
Comment 1 SATHEESARAN 2019-03-22 14:20:36 UTC 
This customer case is the best example where user made a mistake by choosing HE deployment,
instead of 'HC deployment' -> 'use existing configuration'

https://bugzilla.redhat.com/show_bug.cgi?id=1669980
Comment 6 SATHEESARAN 2019-07-12 03:14:11 UTC 
The information same as described in https://bugzilla.redhat.com/show_bug.cgi?id=1722456#c4 should help
Comment 10 bipin 2019-07-17 05:07:44 UTC 
Moving the bug to verified since the contents are added to the doc.