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
(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.
Closing NOTABUG since this already exists in 3.11. Suggest ensuring they are using the latest playbooks and the playbook completes sucessfully.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days