Bug 1939898 - Wrong number of replicas for cluster logging in machine_management/creating-infrastructure-machinesets.adoc
Summary: Wrong number of replicas for cluster logging in machine_management/creating-i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Petr Kovar
QA Contact: Xiaoli Tian
Petr Kovar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-17 09:45 UTC by Sergio G.
Modified: 2024-06-14 00:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-14 17:56:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHDEVDOCS-3082 0 Unprioritized Open Bug 1939898 - Wrong number of replicas for cluster logging in machine_management/creating-infrastructure-machinesets.ado... 2021-06-17 16:32:33 UTC

Description Sergio G. 2021-03-17 09:45:27 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/machine_management/creating-infrastructure-machinesets#infrastructure-moving-logging_creating-infrastructure-machinesets


Section Number and Name: 
6.4.4. Moving OpenShift Logging resources


Describe the issue: 
The text: **You should set your machine set to use at least 6 replicas**. seems to be wrong. The minimal number should be 3.


Suggestions for improvement: 
Set the right number.


Additional information: 
It would be nice if a note about the requirements of such nodes to run the cluster logging is added, but it can also be added in https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/logging/cluster-logging-deploying

Comment 2 Claire Bremble 2022-06-14 17:55:43 UTC
It appears the request has either been completed or is no longer needed as the mentioned problematic text is no longer in the docs. I believe this can be closed.


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