Bug 1611788
| Summary: | [free-int] max virtual memory areas vm.max_map_count [65530] is too low | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Justin Pierce <jupierce> | ||||||
| Component: | Installer | Assignee: | ewolinet | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, juzhao, mmccomas, wsun | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.11.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-10-11 07:23:07 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1472814 [details]
skipping memory changes
Should be in openshift-ansible-3.11.0-0.15.0 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 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 |
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