commit 0c2f3e6b1b598df9a4dd5068b34b20bd38ef37fd
Author: David Ames <email address hidden>
Date: Thu Oct 20 15:59:38 2016 -0700
Fix DNS resolution problems
There are two distinct DNS resolution problems. One, the nodename
reverse DNS resolution. And two, resolution of peers. This attempts
to fix both problems.
Nodename is only required when rabbitmq runs multiple instances on
the same host. Having this set complicates the DNS requirements.
Removing this setting may simplify the DNS problems this charm has
faced.
For peer resolution force the use of hostname rather than dynamically
attempting to resolve one from an IP. Set /etc/hosts with the local
hostname and with each peer.
Standardize the way an IPv4 or IPv6 address is selected throughout
the charm. Standardize the way a hostname is selected throughout the
charm.
Reviewed: https:/ /review. openstack. org/389387 /git.openstack. org/cgit/ openstack/ charm-rabbitmq- server/ commit/ ?id=0c2f3e6b1b5 98df9a4dd5068b3 4b20bd38ef37fd
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0c2f3e6b1b598df 9a4dd5068b34b20 bd38ef37fd
Author: David Ames <email address hidden>
Date: Thu Oct 20 15:59:38 2016 -0700
Fix DNS resolution problems
There are two distinct DNS resolution problems. One, the nodename
reverse DNS resolution. And two, resolution of peers. This attempts
to fix both problems.
Nodename is only required when rabbitmq runs multiple instances on
the same host. Having this set complicates the DNS requirements.
Removing this setting may simplify the DNS problems this charm has
faced.
For peer resolution force the use of hostname rather than dynamically
attempting to resolve one from an IP. Set /etc/hosts with the local
hostname and with each peer.
Standardize the way an IPv4 or IPv6 address is selected throughout
the charm. Standardize the way a hostname is selected throughout the
charm.
Partial-Bug: 1584902 53a52c5a944e8c5 62945e2a6eb
Change-Id: I105eb2684e61a5