Bug 1818101

Summary: Missing a step to taint node in section 4.3.1.2 in managing openshift container storage 4.2 documentation
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Usman Butt <ubutt>
Component: documentationAssignee: Kusuma <kbg>
Status: CLOSED WONTFIX QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2CC: asriram, kbg, khartsoe, ocs-bugs
Target Milestone: ---   
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-05-04 07:26:42 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    

Description Usman Butt 2020-03-27 17:13:36 UTC
Description of problem (please be detailed as possible and provide log
snippests):

In Section 4.3.1.2 of the Managing OpenShift Container Storage 4.2 documentation there is a step missing to apply a taint to the newly deployed node so as to dedicate the node only for storage or at least have a section mentioning about it just like in the deploying the cluster document.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Users will miss this step while scaling out storage nodes which could cause performance issues in production systems.

Is there any workaround available to the best of your knowledge?

Add the step for applying a taint.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 3 Raz Tamir 2020-04-28 15:39:56 UTC
Why taints are part of our docs?
I think this should not be fixed/added