Bug 1337650 - log flooded with Could not map name=xxxx to a UUID when config'd with long hostnames
Summary: log flooded with Could not map name=xxxx to a UUID when config'd with long ho...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On: 1337649
Blocks: 1337652 1337653
TreeView+ depends on / blocked
 
Reported: 2016-05-19 18:10 UTC by Kaleb KEITHLEY
Modified: 2016-12-06 05:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 1337649
: 1337652 (view as bug list)
Environment:
Last Closed: 2016-12-06 05:13:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-05-19 18:27:20 UTC 
REVIEW: http://review.gluster.org/14435 (common-ha: log flooded with Could not map name=xxxx to a UUID) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
Comment 2 Vijay Bellur 2016-05-23 08:55:55 UTC 
COMMIT: http://review.gluster.org/14435 committed in master by Niels de Vos (ndevos) 
------
commit 5cf7a32be8d614e8cd89a01ac06e830cbd693929
Author: Kaleb S KEITHLEY <kkeithle>
Date:   Thu May 19 14:24:08 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: 1337650
    Signed-off-by: Kaleb S KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/14435
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: jiffin tony Thottan <jthottan>
    Reviewed-by: soumya k <skoduri>
Note You need to log in before you can comment on or make changes to this bug.