This changes quite a bit about the assumptions that the charm does to resolve the hostname of the local unit; specifically it now completely skips any direct queries to DNS and just uses socket.gethostname() to set the local nodename - this also gets stored by the leader in leader storage for clustering of followers.
This makes the huge assumption that socket.gethostname() is always resolvable across the peers within a service, but I don't think that is unreasonable.
OK - so I've done some refactoring and come up with:
cs:~james- page/xenial/ rabbitmq- server-bug1584902
This changes quite a bit about the assumptions that the charm does to resolve the hostname of the local unit; specifically it now completely skips any direct queries to DNS and just uses socket. gethostname( ) to set the local nodename - this also gets stored by the leader in leader storage for clustering of followers.
This makes the huge assumption that socket. gethostname( ) is always resolvable across the peers within a service, but I don't think that is unreasonable.