Bug 1576747 - Hosted Engine deployment fails while adding second and third host to the engine with RHV 4.2
Summary: Hosted Engine deployment fails while adding second and third host to the engi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Deploying_RHHI
Version: rhhi-1.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-10 10:28 UTC by SATHEESARAN
Modified: 2019-02-21 05:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: During hosted engine deployment, there is an error in the auto-add second and third host procedure Consequence: The deployment fails with an error though Hosted Engine is successfully deployed Workaround (if any): Manually add the second and third hosts using the RHV-M UI. Result:
Clone Of:
Environment:
Last Closed: 2019-02-21 05:50:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description SATHEESARAN 2018-05-10 10:28:23 UTC
Description of problem:
-----------------------
Hosted Engine deployment fails with the step of adding 2nd and 3rd host to the engine. The customer can proceed though and continue adding the host through RHV manager UI

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHHI 1.1 deployment guide


Expected results:
-----------------
After Hosted engine deployment initiation, user to look for failure in 'adding hosts to engine'. On that occurrence, user can close the cockpit wizard, continue to RHV Manager UI ( URL ) and manually add the other hosts to the cluster

Additional info:

Comment 1 SATHEESARAN 2018-05-10 10:30:13 UTC
Sahina,

Could you look in to the relevant information to be passed to doc team as part of this bug ?

Comment 8 Laura Bailey 2019-02-21 05:50:02 UTC
Closing CURRENTRELEASE since this is now available on access.redhat.com.


Note You need to log in before you can comment on or make changes to this bug.