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:
REVIEW: https://review.gluster.org/21034 (rpc: log frame->root->unique along with XID) posted (#1) for review on master by Milind Changire
REVIEW: https://review.gluster.org/21034 (rpc: log fuse unique ID along with gluster XID) posted (#3) for review on master by Milind Changire
REVIEW: https://review.gluster.org/21034 (rpc: log fuse unique ID along with gluster XID) posted (#7) for review on master by Milind Changire
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>
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/