Bug 1337649

Summary:	log flooded with Could not map name=xxxx to a UUID when config'd with long hostnames
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	nfs-ganesha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED ERRATA	QA Contact:	Shashank Raj <sraj>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, rcyriac, rhinduja, sashinde, sraj
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.9-7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:
Clones:	1337650 (view as bug list)		Environment:
Last Closed:	2016-06-23 05:23:52 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:
Bug Blocks:	1311817, 1337650, 1337652, 1337653

Description Kaleb KEITHLEY 2016-05-19 18:07:49 UTC

Description of problem:

When the cluster is configured with long (FQDN) cluster particpants the log is flooded with "Could not map name=r7n1 to a UUID" notices


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Atin Mukherjee 2016-05-25 05:53:52 UTC

Upstream mainline : http://review.gluster.org/14435
3.8 : http://review.gluster.org/14436
3.7 : http://review.gluster.org/14437

All the above patches are merged.

Comment 7 Shashank Raj 2016-06-01 13:52:47 UTC

Verified this bug with latest glusterfs-3.7.9-7 and nfs-ganesha-2.3.1-7 build and no such messages "Could not map name=xxxx to a UUID" are seen in /var/log/messages.

System is configured with long hostnames as below:

dhcp46-247.lab.eng.blr.redhat.com
dhcp46-26.lab.eng.blr.redhat.com
dhcp47-139.lab.eng.blr.redhat.com
dhcp46-202.lab.eng.blr.redhat.com

Since the earlier reported issue is not seen with latest builds, marking this bug as Verified.

Comment 9 errata-xmlrpc 2016-06-23 05:23:52 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1240