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'
https://github.com/openshift/openshift-ansible/pull/10328
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