Bug 1611788 – [free-int] max virtual memory areas vm.max_map_count [65530] is too low

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1611788 - [free-int] max virtual memory areas vm.max_map_count [65530] is too low

Summary:	[free-int] max virtual memory areas vm.max_map_count [65530] is too low

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.11.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	ewolinet
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-02 14:01 EDT by Justin Pierce
Modified:	2018-10-11 03:23 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-10-11 03:23:07 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Error output from crashing pod (4.63 KB, text/plain) 2018-08-02 14:01 EDT, Justin Pierce	no flags	Details
skipping memory changes (1.24 KB, text/plain) 2018-08-02 15:20 EDT, Justin Pierce	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:2652	None	None	None	2018-10-11 03:23 EDT

Groups: None (edit)

Description Justin Pierce 2018-08-02 14:01:03 EDT

Created attachment 1472803 [details]
Error output from crashing pod

Description of problem:
After attempted upgrade to OCP logging 3.11, es pods in crash loop due to memory requirements.

Version-Release number of the following components:
v3.11.0-0.10.0

How reproducible:
Presently occurring in free-int cluster.

Steps to Reproduce:
1. Standard logging upgrade from v3.10 to v3.11.0-0.10.0

Comment 1 Justin Pierce 2018-08-02 15:20 EDT

Created attachment 1472814 [details]
skipping memory changes

Comment 2 ewolinet 2018-08-03 17:52:05 EDT

fixed by https://github.com/openshift/openshift-ansible/pull/9267

Comment 3 Scott Dodson 2018-08-14 17:24:37 EDT

Should be in openshift-ansible-3.11.0-0.15.0

Comment 4 Junqi Zhao 2018-08-15 03:34:16 EDT

vm.max_map_count is 262144 for ES pod, but there is "java.io.IOException: No space left on device" for one ES pod, see Bug 1616169.

Close this defect, ES IO issues will be tracked by Bug 1616169

Comment 6 errata-xmlrpc 2018-10-11 03:23:07 EDT

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-2018:2652

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