Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1673967

Summary: [DOCS] Adding OSD manually should include setting 'noup'
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED CURRENTRELEASE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.2CC: agunn, kdreyer
Target Milestone: z1   
Target Release: 3.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: 2019-08-26 06:56:03 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: 1668330    

Description Mike Hackett 2019-02-08 15:40:30 UTC 
Description of problem:
The RHCS 3.2 Operations guide for manually adding an OSD node should include setting 'noup' flag in the clsuter prior to adding the OSD node. If this is not set and the OSD's are activated they can be overloaded with PG"s causing the cluster to enter HEALTH_ERR. This flag is automatically set when adding an OSD node via Ansible so should be set when adding manually as well.

Doc section requiring update:

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/operations_guide/managing-the-storage-cluster-size#adding-a-ceph-osd-using-the-command-line-interface-ops

Release Notes stating 'noup' flag being set in RHCS 3.2 when adding OSD node:

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3.2/html-single/release_notes/#the_literal_ceph_ansible_literal_utility

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

3.2