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

Bug 1791997

Summary:	Backport request for 3.11 re: BZ 1739322
Product:	OpenShift Container Platform	Reporter:	Greg Rodriguez II <grodrigu>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED NOTABUG	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, mifiedle, mirwin, scuppett
Target Milestone:	---
Target Release:	3.11.z
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-01-28 20:53:50 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:
Bug Depends On:	1739322
Bug Blocks:

Description Greg Rodriguez II 2020-01-16 20:22:35 UTC

Description of problem:
Customer is experiencing the problem described in BZ 1729322 [1] but in their OCP 3.11 environment.  Issue was resolved with a 4.1 Errata [2] and customer would like to push for a 3.11 backport.

Running 'sysctl -w vm.max_map_count=262144' on each of their infra nodes did resolve the issue, which is discussed as a workaround in the BZ [1].

Customer would like to know if an official fix to resolve this issue is available in 3.11 without the need to run the above command.

Version-Release number of selected component (if applicable):
OCP 3.11

Additional info:
[1]  https://bugzilla.redhat.com/show_bug.cgi?id=1739322
[2]  https://access.redhat.com/errata/RHBA-2019:2547

Comment 2 Jeff Cantrill 2020-01-17 17:28:13 UTC

(In reply to Greg Rodriguez II from comment #0)
> Description of problem:
> Customer is experiencing the problem described in BZ 1729322 [1] but in
> their OCP 3.11 environment.  Issue was resolved with a 4.1 Errata [2] and
> customer would like to push for a 3.11 backport.
> 
> Running 'sysctl -w vm.max_map_count=262144' on each of their infra nodes did
> resolve the issue, which is discussed as a workaround in the BZ [1].

There is no way to run openshift-loggign in 3.11 without this setting; Elasticsearch has a hard fail if it detects its any other value.  Please ensure you are using the latest playbooks which already include [1] 

[1] https://github.com/openshift/openshift-ansible/blob/release-3.11/playbooks/openshift-logging/private/config.yml#L94

> 
> Customer would like to know if an official fix to resolve this issue is
> available in 3.11 without the need to run the above command.

The installer during running logging install should already update this setting.

Comment 3 Jeff Cantrill 2020-01-28 20:53:50 UTC

Closing NOTABUG since this already exists in 3.11. Suggest ensuring they are using the latest playbooks and the playbook completes sucessfully.

Comment 4 Red Hat Bugzilla 2023-09-18 00:19:50 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days