Elastic Search fails on instance with "Global" IP address

[Sean Shuping]

In My case I'm using Juju to control my MAAS cloud.

If an instance has a true public IP address the application fails to initialize.

---log snip ---
No up-and-running site-local (private) addresses found, got [name:lo (lo), name:ens160 (ens160)]
---end snip ---

Further more on the model, application states Ports:9200/tcp Message:Ready which is not true.

I think the validation of if the app is ready should wait longer.

systemctl status elasticsearch states 'running' immediately after starting service but about 5 seconds later status will change to 'failed'.

[Xav Paice (xavpaice)]

I know this has been a long time since the bug report, and details may no longer be available. If this can be reproduced now, could you share a more full juju unit log from the Elastic unit, as well as any Elastic logs themselves and /var/syslog, and some details on the model itself? We really need to understand the network spaces in use, as well as what's killing Elastic.

[Launchpad Janitor (janitor)]

[Expired for Elasticsearch Charm because there has been no activity for 60 days.]