Bug 1740558

Summary: The tuned pod doesn't set max virtual memory areas vm.max_map_count for elasticsearch pod in node.
Product: OpenShift Container Platform Reporter: Qiaoling Tang <qitang>
Component: Node Tuning OperatorAssignee: Jiří Mencák <jmencak>
Status: CLOSED ERRATA QA Contact: Mike Fiedler <mifiedle>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: akamra, anli, jmencak, mifiedle, sejug, vlaad
Target Milestone: ---Keywords: Regression
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1739322 Environment:
Last Closed: 2019-10-16 06:35:53 UTC Type: ---
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: 1739322    
Bug Blocks:    

Comment 6 Mike Fiedler 2019-08-28 15:31:57 UTC 
verified on 4.2.0-0.nightly-2019-08-28-083236

# oc debug node/ip-10-0-167-4.us-west-2.compute.internal
Starting pod/ip-10-0-167-4us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.167.4
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host
sh-4.4# sysctl vm.max_map_count
vm.max_map_count = 262144


Where that node is has ES running on it.
Comment 7 errata-xmlrpc 2019-10-16 06:35:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922