Bug 1356503

Summary:	Add trouble shooting section for failed nodes while import cluster flow
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Shubhendu Tripathi <shtripat>
Component:	documentation	Assignee:	Rakesh <rghatvis>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Kudlej <mkudlej>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2	CC:	mkudlej, nthomas, sankarshan
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:34:02 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:	1332984

Description Shubhendu Tripathi 2016-07-14 09:29:05 UTC

Description of problem:
A trouble shooting section needs to be added in admin guide for tackling failed nodes while import cluster flow.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Martin Kudlej 2016-08-11 10:26:31 UTC

Issue 2:
"The repositories should not contain any unsigned RPMs or else ceph-installer fails. Ensure proper keys are installed and if gpgcheck=0 is set for the repositories in /etc/yum.repos.d/*.repo files."

I think this text is a little bit confusing. Users will use only CDN repositories so I think it is better to have link here to book about subscription manager and note that user should check if repositories are set OK.

Issue 3-> Cause 2:
I think here should be some description about Console database, because user doesn't know what is it and where to find it and how to do step 1. in resolution:
 Remove the specific records from table storage_nodes of Storage Console database. 

Same in 12.3 -> issue 1 -> Cause 2 -> Resolution-. step 7:
 Remove the node records from Storage Console database. 
Same in next issue point 3:
 Remove the cluster from Storage Console database. 

I see that there is note, but I think that is not enough. I expect that we have also book about mongodb, because RH distributes it in Software Collections.

Same at the end of chapter:
Under such scenarios, remove the cluster details from Storage Console database (if cluster records are there, usee th Unmanage and Forget feature). Clear all the nodes and re-create the cluster in Storage Console.