Master_not_discovered_exception after upgrade to Ubuntu Jammy and Docker 28.0.1

Elastic Stack Elasticsearch
11

I've tried removing the network.bind_host entry. There's still a problem but with a difference. I no longer see the exceptions in the logs. Instead I see the following messages over and over. It does seem that there's a probem with how the pmd43test-elastic-1.platform-lab.cloud.xxx.org FDN is getting resolved. I'm going to try substituting the IP addresses of the hosts on the respective networks in the elasticsearch.yaml instead of their host names and see if that works. There's got to be something I'm doing in this deployment that's messing things up since it works without the OS and docker version changes I've made.

{"type": "server", "timestamp": "2025-03-03T19:15:52,057Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elastic-docker-cluster", "node.name": "pmd43test-elastic-1", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [pmd43test-elastic-1, pmd43test-elastic-2, pmd43test-elastic-3] to bootstrap a cluster: have discovered [{pmd43test-elastic-1}{5VmndbPjRFucYyvO6BATUg}{AvxbRMHpQPKLPMlE1ZBQKw}{pmd43test-elastic-1.platform-lab.cloud.xxx.org}{127.0.1.1:9300}{cdfhimrstw}]; discovery will continue using [172.17.0.96:9300, 172.17.2.190:9300] from hosts providers and [{pmd43test-elastic-1}{5VmndbPjRFucYyvO6BATUg}{AvxbRMHpQPKLPMlE1ZBQKw}{pmd43test-elastic-1.platform-lab.cloud.xxx.org}{127.0.1.1:9300}{cdfhimrstw}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }


{"type": "server", "timestamp": "2025-03-03T19:15:52,125Z", "level": "WARN", "component": "o.e.d.PeerFinder", "cluster.name": "elastic-docker-cluster", "node.name": "pmd43test-elastic-1", "message": "address [172.17.2.190:9300], node [null], requesting [false] connection failed: [][172.17.2.190:9300] connect_exception: Connection refused: pmd43test-elastic-3.ops.platform-lab.intra/172.17.2.190:9300: Connection refused" }

{"type": "server", "timestamp": "2025-03-03T19:15:52,126Z", "level": "WARN", "component": "o.e.d.PeerFinder", "cluster.name": "elastic-docker-cluster", "node.name": "pmd43test-elastic-1", "message": "address [172.17.0.96:9300], node [null], requesting [false] connection failed: [][172.17.0.96:9300] connect_exception: Connection refused: pmd43test-elastic-2.ops.platform-lab.intra/172.17.0.96:9300: Connection refused" }
1 Like