Bug 1818101 - Missing a step to taint node in section 4.3.1.2 in managing openshift container storage 4.2 documentation
Summary: Missing a step to taint node in section 4.3.1.2 in managing openshift contain...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: documentation
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 4.4.0
Assignee: Kusuma
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks: 1826040
TreeView+ depends on / blocked
 
Reported: 2020-03-27 17:13 UTC by Usman Butt
Modified: 2020-05-04 07:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 07:26:42 UTC
Embargoed:


Attachments (Terms of Use)

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


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