Bug 1623408

Summary: rpc: log fuse request ID with gluster transaction ID
Product: [Community] GlusterFS Reporter: Milind Changire <mchangir>
Component: rpcAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-23 15:18:02 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 Milind Changire 2018-08-29 09:58:37 UTC
Description of problem:
for better traceability between fuse requests and gluster requests a mapping needs to be established in the logs between the two IDs

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-08-29 10:03:32 UTC
REVIEW: https://review.gluster.org/21034 (rpc: log frame->root->unique along with XID) posted (#1) for review on master by Milind Changire

Comment 2 Worker Ant 2018-08-29 10:54:31 UTC
REVIEW: https://review.gluster.org/21034 (rpc: log fuse unique ID along with gluster XID) posted (#3) for review on master by Milind Changire

Comment 3 Worker Ant 2018-08-30 04:42:49 UTC
REVIEW: https://review.gluster.org/21034 (rpc: log fuse unique ID along with gluster XID) posted (#7) for review on master by Milind Changire

Comment 4 Worker Ant 2018-08-30 13:04:10 UTC
COMMIT: https://review.gluster.org/21034 committed in master by "Raghavendra G" <rgowdapp> with a commit message- rpc: log fuse unique ID along with gluster XID

for better traceability between fuse requests and gluster requests a
mapping needs to be established in the logs between the two IDs

BUG: 1623408
Change-Id: I0ef82fe69c1ad7d0ce9e3ac4f35cd82aa6e9bca9
fixes: bz#1623408
Signed-off-by: Milind Changire <mchangir>

Comment 5 Shyamsundar 2018-10-23 15:18:02 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/