Bug 1800522

Summary:	Often getting "Locking failed on <node>. Please check log file for details."
Product:	[Community] GlusterFS	Reporter:	Lars Berntzon <lars.berntzon>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs, pasik, srakonde
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-10 04:07:44 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 Lars Berntzon 2020-02-07 10:35:13 UTC

Description of problem:
Running the command "gluster volume status <volume>" on two separate nodes often gives the error:
   Locking failed on <node>. Please check log file for details.


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

Ubuntu 18 running gluster 6.7-ubuntu1~bionic1

How reproducible:

Easy.


Steps to Reproduce:

1. Run a while loop on first gluster nodes like:
      while :; do gluster volume status <volume>; done

2. Run same loop on other node simultaneously.

Actual results:

Both loops will start to randomly fail with the message:
      Locking failed on <node>. Please check log file for details.


Expected results:
   Status reports on both nodes.

Additional info:

Comment 1 Sanju 2020-02-10 04:07:44 UTC

"gluster volume status" collects information from all the nodes to display the output on the originator node. So, it needs the lock on every node. When we execute this command simultaneously on different nodes of trusted storage pool, the locking fails and the error is expected.

Hence, closing the bug as not a bug.

Thanks,
Sanju