Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1023636

Summary:	Inconsistent UUID's not causing an error that would stop the system
Product:	[Community] GlusterFS	Reporter:	Dean Bruhn <deanbruhn>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.2	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:32 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:

Description Dean Bruhn 2013-10-26 11:59:15 UTC

Description of problem:
An issue came up where my log files over ran my /var partition, this caused my volume configurations to become corrupt on several servers. Because the of the issue I needed to copy the config files from a known good host using the gluster commands to do so. 

Part of the resolution was to re-probe the servers to get them back in sync. I ended up with several servers who's UUID's did not match the peer files across the cluster. The gluster commands would work intermittently if I spammed the commands and the cluster and volume was functioning, but not optimally, it would suffer a lot of what seemed to be random disconnects, etc. 

What I was seeing was that the glusterd.info file on server1 would have a UUID of 6e5df7ab-4440-49b2-9aa7-a5984391b5f5, but it's peer files on each of the other 10 servers would either reference the correct 6e5df7ab-4440-49b2-9aa7-a5984391b5f5 or 35e62be3-752e-48aa-aa15-dc68abfaf06f (these UUID's are only examples). 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

The system ran in an inconsistent state even though the UUID's configurations didn't match across the cluster. 


Expected results:

The system would not function until the UUID's were corrected. 


Additional info:

It might be useful to have some sort of UUID consistency check algorithm that either stops the system and throws an error, or is intelligent enough to correct the problem.

Comment 1 Niels de Vos 2014-11-27 14:54:35 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.