Bug 1803733

Summary: [LSO] Document how to replace node - VMware and Baremetal
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Pratik Surve <prsurve>
Component: documentationAssignee: Kusuma <kbg>
Status: CLOSED CURRENTRELEASE QA Contact: Pratik Surve <prsurve>
Severity: high Docs Contact:
Priority: high    
Version: 4.3CC: asriram, bchardim, dcain, ebenahar, jarrpa, khartsoe, madam, mmuench, nberry, ocs-bugs, olakra, owasserm, ratamir, sabose, sagrawal, sdudhgao, sostapov
Target Milestone: ---Keywords: Reopened
Target Release: OCS 4.4.0   
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: 2020-06-08 06:06:39 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: 1826040    

Comment 3 Jose A. Rivera 2020-02-25 15:26:47 UTC
OSDs are not expected to be able to migrate between nodes in baremetal environments. To make use of a device on a new node, the relevant OSD Deployment must be deleted so that a new one can be created to replace it.

Several of these nodes are also reporting insufficient memory. For baremetal BZs, please also include the CPU and Memory resources on the nodes, available in the oc describe node output, since we can't guarantee what those numbers are.

Based on my current understanding of the problem, I'll be closing this as not a bug. If I have a misunderstanding or further information is required, please feel free to reopen.

Comment 4 Elad 2020-02-25 15:30:24 UTC
Hi Jose, 

I'd like to keep this BZ open, at least until we have the proper procedure for node replacement with BM.

Comment 5 Jose A. Rivera 2020-02-25 15:33:24 UTC
In that case, moving this to documentation and updating the BZ subject.

Comment 10 Anjana Suparna Sriram 2020-03-26 15:30:25 UTC
*** Bug 1813865 has been marked as a duplicate of this bug. ***