Bug 1609131

Summary: ES and Kibana pod couldn't be ready.
Product: OpenShift Container Platform Reporter: Qiaoling Tang <qitang>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED DUPLICATE QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, rmeggins
Target Milestone: ---   
Target Release: 3.11.0   
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: 2018-07-27 10:11:42 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:

Comment 2 Anping Li 2018-07-27 10:10:48 UTC
It is a playbook bug, the PLAY [Update vm.max_map_count for ES 5.x] was skipped.
 
The elasticsearch pod became ready after I configured the  vm.max_map_count manually.

PLAY [Update vm.max_map_count for ES 5.x] **************************************
META: ran handlers

TASK [Checking vm max_map_count value] *****************************************
task path: /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/private/config.yml:85
Friday 27 July 2018  08:53:10 +0000 (0:00:00.053)       0:00:37.868 *********** 
skipping: [qe-qitang-311-gcenode-1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Updating vm.max_map_count value] *****************************************
task path: /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/private/config.yml:90
Friday 27 July 2018  08:53:10 +0000 (0:00:00.023)       0:00:37.892 *********** 
skipping: [qe-qitang-311-gcenode-1] => {"changed": false, "skip_reason": "Conditional result was False"}
META: ran handlers
META: ran handlers

PLAY [Remove created 99-elasticsearch sysctl] **********************************
META: ran handlers

Comment 3 Anping Li 2018-07-27 10:11:42 UTC

*** This bug has been marked as a duplicate of bug 1609138 ***