+++ This bug was initially created as a clone of Bug #1241274 +++
In a user environment, a server might be migrated/restarted with a different IP address than it had before. DNS has been updated to point the old name at the new address, and thus clients can still reconnect to it OK, but other servers fail to recognize it as a cluster member because of the address change. In this particular case, the problem is related to containerization of the servers, but it can also occur with bare-metal failover solutions. The key factor is really that the user is unable/unwilling to configure their routing so that a floating service address can be reassigned to a new physical machine in case of failover or migration.
Extra detail: the problem occurs because the *recipient* of a "peer probe" message initially stores the sender's string-valued IP address instead of its name. If we then probe in the other direction using that peer's name, we update our peer record with that as well, but that's a total hack and doesn't seem totally foolproof either. A better solution is to store and subsequently compare against reverse-resolved host names for probes we receive, whenever such names are available. Such an approach would be effectively immune to such address changes (though it doesn't solve the general problem of DNS errors or misconfiguration).
--- Additional comment from Anand Avati on 2015-07-08 17:35:17 EDT ---
REVIEW: http://review.gluster.org/11587 (glusterd: use a real host name (instead of numeric) when we have one) posted (#1) for review on master by Jeff Darcy (email@example.com)
--- Additional comment from Anand Avati on 2015-07-09 08:48:04 EDT ---
REVIEW: http://review.gluster.org/11587 (glusterd: use a real host name (instead of numeric) when we have one) posted (#2) for review on master by Jeff Darcy (firstname.lastname@example.org)
--- Additional comment from Anand Avati on 2015-07-10 08:35:48 EDT ---
COMMIT: http://review.gluster.org/11587 committed in master by Krishnan Parthasarathi (email@example.com)
Author: Jeff Darcy <firstname.lastname@example.org>
Date: Wed Jul 8 09:52:15 2015 -0400
glusterd: use a real host name (instead of numeric) when we have one
Signed-off-by: Jeff Darcy <email@example.com>
Reviewed-by: Shyamsundar Ranganathan <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
REVIEW: http://review.gluster.org/11624 (glusterd: use a real host name (instead of numeric) when we have one) posted (#1) for review on release-3.7 by Krishnan Parthasarathi (email@example.com)
*** Bug 1242546 has been marked as a duplicate of this bug. ***
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.3, please open a new bug report.
glusterfs-3.7.3 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.