Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1811348

Summary: Documentation incorrectly advises to edit node-config.yaml instead of ConfigMaps
Product: OpenShift Container Platform Reporter: Christian Koep <ckoep>
Component: DocumentationAssignee: Michael Burke <mburke>
Status: CLOSED CURRENTRELEASE QA Contact: Sunil Choudhary <schoudha>
Severity: low Docs Contact: Vikram Goyal <vigoyal>
Priority: low    
Version: 3.11.0CC: aos-bugs, jchaloup, jokerman, schoudha
Target Milestone: ---   
Target Release: ---   
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-04-09 18:01:27 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:

Description Christian Koep 2020-03-07 21:50:30 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/cluster_administration/admin-guide-sysctls

Section Number and Name: 

34.5. Enabling unsafe sysctls

Describe the issue: 

The documentation (in version 3.11) should advise to adjust node ConfigMaps instead of editing  /etc/origin/node/node-config.yaml directly.

Suggestions for improvement: 

https://access.redhat.com/solutions/4830591 describes the correct process.

Additional information:

Comment 2 Michael Burke 2020-04-01 15:50:40 UTC
Christian --

Please see https://github.com/openshift/openshift-docs/pull/20812.

Do we need all of the steps in the solution? Previously, we instructed users to edit the config map and restart the node service. Nothing about updating the SCC or editing the deploymentConfigs.

Comment 8 Kevin Lamenzo 2020-05-07 13:07:59 UTC
*** Bug 1754403 has been marked as a duplicate of this bug. ***