Bug 1337653

Summary:	log flooded with Could not map name=xxxx to a UUID when config'd with long hostnames
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	common-ha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	bugs, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.12	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1337652	Environment:
Last Closed:	2016-06-21 10:45:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1337649, 1337650, 1337652
Bug Blocks:

Comment 1 Vijay Bellur 2016-05-19 18:32:19 UTC

REVIEW: http://review.gluster.org/14437 (common-ha: log flooded with Could not map name=xxxx to a UUID) posted (#1) for review on release-3.7 by Kaleb KEITHLEY (kkeithle)

Comment 2 Vijay Bellur 2016-05-23 09:36:53 UTC

COMMIT: http://review.gluster.org/14437 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) 
------
commit b632ff7e3f614c46d9209f87847a9c0c0892e51e
Author: Kaleb S KEITHLEY <kkeithle>
Date:   Thu May 19 14:31:31 2016 -0400

    common-ha: log flooded with Could not map name=xxxx to a UUID
    
    When the cluster is configured with long (FQDN) cluster members
    the log is flooded with "Could not map name=$shortname to a UUID"
    notices, and setting/getting the attribute is failing
    
    Change-Id: I954d8cef7115659cc9c8b23dae75a5a247dc5db7
    BUG: 1337653
    Signed-off-by: Kaleb S KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/14437
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Kaushal 2016-06-28 12:18:31 UTC

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.12, please open a new bug report.

glusterfs-3.7.12 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user