Bug 1636248
| Summary: | not enough master nodes discoverd because service logging-es-cluster is not headless | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.11.0 | CC: | aos-bugs, jupierce, qitang, rmeggins |
| 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: | 2018-11-20 03:10:46 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: | |||
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:3537 |
Description of problem: The service 'logging-es-cluster' was not configured to be headless resulting in the es pods being unable to cluster. The logged error: [2018-10-03T14:50:42,029][WARN ][o.e.d.z.ZenDiscovery ] [logging-es-data-master-2ohdnb9t] not enough master nodes discovered during pinging (found [[Candidate{node={logging-es-data-master-2ohdnb9t}{ubXkUISYQ5qT88STWcphjw}{bq_DwgYCT-Osb7v4e7pRjA}{10.129.6.241}{10.129.6.241:9300}, clusterStateVersion=-1}]], but needed [2]), pinging again [2018-10-03T14:50:45,030][WARN ][o.e.d.z.ZenDiscovery ] [logging-es-data-master-2ohdnb9t] not enough master nodes discovered during pinging (found [[Candidate{node={logging-es-data-master-2ohdnb9t}{ubXkUISYQ5qT88STWcphjw}{bq_DwgYCT-Osb7v4e7pRjA}{10.129.6.241}{10.129.6.241:9300}, clusterStateVersion=-1}]], but needed [2]), pinging again Version-Release number of selected component (if applicable): 3.11 How reproducible: Always Additional info: Resolvable be recreating the service with 'clusterIP: None'