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:
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
The information same as described in https://bugzilla.redhat.com/show_bug.cgi?id=1722456#c4 should help
Moving the bug to verified since the contents are added to the doc.