### Author:  [@bob1985](https://discuss.elastic.co/u/bob1985)
#### Post date: [October 21, 2020, 2:48am UTC](https://discuss.elastic.co/t/elasticsearch-7-8-1-on-openshift-4-5-3-pods/252758/1 "2020-10-21T02:48:49Z")
Elasticsearch 7.8.1 on Openshift 4.5 - 3 Pods
Hi,
Can you please help on below error:
```
"message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [ ] is empty on this node: have discovered [{es-cluster-0}
```
elastic-app.yaml
```
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: es-cluster
namespace: infra
spec:
serviceName: elasticsearch
replicas: 3
selector:
matchLabels:
app: elasticsearch
template:
metadata:
labels:
app: elasticsearch
spec:
containers:
- name: elasticsearch
image: /elasticsearch:7.8.1
resources:
limits:
cpu: 1000m
memory: 4Gi
requests:
cpu: 100m
memory: 1Gi
ports:
- containerPort: 9200
name: rest
protocol: TCP
targetPort: 9200
- containerPort: 9300
name: inter-node
protocol: TCP
volumeMounts:
- name: data
mountPath: /usr/share/elasticsearch/data
env:
- name: cluster.name
value: infra-efk
- name: node.name
valueFrom:
fieldRef:
fieldPath: metadata.name
#- name: discovery.zen.ping.unicast.hosts
# value: "es-cluster-0.elasticsearch,es-cluster-1.elasticsearch,es-cluster-2.elasticsearch"
- name: discovery.zen.ping_timeout
value: "60s"
- name: discovery.seed_hosts
value: "es-cluster-0.elasticsearch,es-cluster-1.elasticsearch,es-cluster-2.elasticsearch"
- name: discovery.zen.minimum_master_nodes
value: "3"
- name: cluster.initial_master_nodes
value: "es-cluster-0.elasticsearch,es-cluster-1.elasticsearch,es-cluster-2.elasticsearch"
- name: ES_JAVA_OPTS
value: "-Xms512m -Xmx512m"
# - name: logger.org.elasticsearch
# value: TRACE
- name: logger.org.elasticsearch.discovery
value: TRACE
volumeClaimTemplates:
- metadata:
name: data
labels:
app: elasticsearch
spec:
accessModes: ["ReadWriteOnce"]
storageClassName: px-block-replicated
resources:
requests:
storage: 10Gi
```
px-elastic-svc.yaml
```
kind: Service
apiVersion: v1
metadata:
name: elasticsearch
labels:
app: elasticsearch
spec:
selector:
app: elasticsearch
clusterIP: None
ports:
- port: 9200
name: rest
- port: 9300
name: inter-node
```
Here are the trace logs:
[https://controlc.com/11f0dfed](https://controlc.com/11f0dfed)
- curl on port 9200 is working fine with just elasticsearch version information.
- curl on port 9200 is not working if cluster pretty print is asked giving error master node not found kind of exception. I don't have the exact exception with me.
- telnet from one node to other node on port 9200 and 9300 is working fine as well. I have tested between multiple nodes.
Can you please help with the issue as the master node is not getting recognized at all?
Reference URL for the cluster: [https://www.digitalocean.com/community/tutorials/how-to-set-up-an-elasticsearch-fluentd-and-kibana-efk-logging-stack-on-kubernetes](https://EFK)
---
### Author:  [@bob1985](https://discuss.elastic.co/u/bob1985)
#### Post date: [October 22, 2020, 6:59am UTC](https://discuss.elastic.co/t/elasticsearch-7-8-1-on-openshift-4-5-3-pods/252758/12 "2020-10-22T06:59:10Z")
Hi,
Can someone help on this?
Thanks
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 22, 2020, 6:59am UTC](https://discuss.elastic.co/t/elasticsearch-7-8-1-on-openshift-4-5-3-pods/252758/13 "2020-10-22T06:59:33Z")
Please be patient in waiting for responses to your question and refrain from pinging multiple times asking for a response or opening multiple topics for the same question. This is a community forum, it may take time for someone to reply to your question. For more information please refer to the [Community Code of Conduct](https://www.elastic.co/community/codeofconduct) specifically the section "Be patient". Also, please refrain from pinging folks directly, this is a forum and anyone that participates might be able to assist you.
If you are in need of a service with an SLA that covers response times for questions then you may want to consider talking to us about a [subscription](https://www.elastic.co/subscriptions).
It's fine to answer on your own thread after 2 or 3 days (not including weekends) if you don't have an answer.
---
### Author:  [@weizenberg](https://discuss.elastic.co/u/weizenberg)
#### Post date: [November 4, 2020, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-7-8-1-on-openshift-4-5-3-pods/252758/14 "2020-11-04T08:32:16Z")
Hey,
I have the same issue on Openshift 4.5.13 with the official Elastic operator (1.2.1). I configured 1 master and 3 data / ingest nodes, it worked for a while and then stopped suddenly with the following error:
` {"type": "server", "timestamp": "2020-11-04T08:04:01,184Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elk", "node.name": "elk-es-master-elk-0", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{elk-es-master-elk-0}{Mp9d5Hl1RpaPZqrpUh7M4w}{iZ04erfiSDuUpM5W_ZFwBQ}{10.128.0.90}{10.128.0.90:9300}{lmr}{ml.machine_memory=8589934592, xpack.installed=true, transform.node=false, ml.max_open_jobs=20}]; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304, [::1]:9305] from hosts providers and [{elk-es-master-elk-0}{Mp9d5Hl1RpaPZqrpUh7M4w}{iZ04erfiSDuUpM5W_ZFwBQ}{10.128.0.90}{10.128.0.90:9300}{lmr}{ml.machine_memory=8589934592, xpack.installed=true, transform.node=false, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }`
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 2, 2020, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-7-8-1-on-openshift-4-5-3-pods/252758/15 "2020-12-02T08:32:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.