Bug 1356503 - Add trouble shooting section for failed nodes while import cluster flow
Summary: Add trouble shooting section for failed nodes while import cluster flow
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: documentation
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2
Assignee: Rakesh
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On:
Blocks: 1332984
TreeView+ depends on / blocked
 
Reported: 2016-07-14 09:29 UTC by Shubhendu Tripathi
Modified: 2018-11-19 05:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:34:02 UTC
Embargoed:


Attachments (Terms of Use)

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.


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