Bug 1337652

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-haAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.8.0CC: bugs, storage-qa-internal
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1337650
: 1337653 (view as bug list) Environment:
Last Closed: 2016-06-16 14:07:31 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    
Bug Blocks: 1337653    

Comment 1 Vijay Bellur 2016-05-19 18:30:16 UTC
REVIEW: http://review.gluster.org/14436 (common-ha: log flooded with Could not map name=xxxx to a UUID) posted (#1) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)

Comment 2 Vijay Bellur 2016-05-23 08:19:11 UTC
REVIEW: http://review.gluster.org/14436 (common-ha: log flooded with Could not map name=xxxx to a UUID) posted (#2) for review on release-3.8 by Niels de Vos (ndevos)

Comment 3 Vijay Bellur 2016-05-23 09:36:36 UTC
COMMIT: http://review.gluster.org/14436 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) 
------
commit 2f278fa9b91b7e81e0d93ec44f486f12bdc3f50b
Author: Kaleb S KEITHLEY <kkeithle>
Date:   Thu May 19 14:29:20 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
    
    Backport of:
    > Change-Id: I954d8cef7115659cc9c8b23dae75a5a247dc5db7
    > Reviewed-on: http://review.gluster.org/14435
    > BUG: 1337650
    > Signed-off-by: Kaleb S KEITHLEY <kkeithle>
    
    Change-Id: I954d8cef7115659cc9c8b23dae75a5a247dc5db7
    BUG: 1337652
    Signed-off-by: Kaleb S KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/14436
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Smoke: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2016-06-16 14:07: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.8.0, please open a new bug report.

glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user