Bug 1122807

Summary:	[RFE] Log a checksum of the new client volfile after a graph change.
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, smohan
Target Milestone:	---	Keywords:	Improvement, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-27 17:17:50 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 Joe Julian 2014-07-24 06:53:52 UTC

Description of problem:

There's no way to know if a client failed to retrieve its new vol file after a graph change. If there was a sha1sum some other consistent checksum, we could easily check all our client logs to ensure the change was completed.

Comment 1 Gaurav Kumar Garg 2014-12-22 12:17:42 UTC

Joe,
you can easily check the checksum in client log. but what if you dont have permission in storage node to see actual checksum of volfile.

Regards
Gaurav

Comment 2 Joe Julian 2014-12-22 16:24:05 UTC

Since any user that can mount a volume will have access to that volume's log file, that should be sufficient. Typically this will only be used for diagnostics or monitoring with root access anyway.

Perhaps a future enhancement could add that to "volume status client"  but this should be sufficient for now.

Comment 3 Yaniv Kaul 2019-04-27 17:17:50 UTC

Closing for the time being due to lack of priority and resources to implement.