Bug 1571517
Summary: | ansible playbook fails as ES pod cannot get ready (Waiting for Quorum due to cluster deployment) | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Rajnikant <rkant> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED WORKSFORME | QA Contact: | Anping Li <anli> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.0 | CC: | aos-bugs, ewolinet, rkant, rmeggins |
Target Milestone: | --- | ||
Target Release: | 3.7.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: | 2018-05-01 19:31:28 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: |
Description
Rajnikant
2018-04-25 03:39:14 UTC
I have reservations that simply adding wait of 30 seconds will consistently resolve this issue. What about if the cluster takes a long time to pull the new images? What if Elasticsearch does not have enough memory and it takes longer then 30 seconds to initialize itself? What version of openshift-ansible is being run against this? This should have been resolved already by [1] which prevents doing a health check against each ES node when we are scaling up [2]. Looking at the snippet you pasted, it seems you do not have the latest fixes. [1] https://github.com/openshift/openshift-ansible/commit/15933df93f37e6fa3e70c2f724504c97ed109e3b [2] https://github.com/openshift/openshift-ansible/blob/15933df93f37e6fa3e70c2f724504c97ed109e3b/roles/openshift_logging_elasticsearch/tasks/restart_es_node.yml#L6 |