Bug 1614142 - Fix the grammar error in the rpc log
Summary: Fix the grammar error in the rpc log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 04:42 UTC by Nigel Babu
Modified: 2018-10-23 15:16 UTC (History)
1 user (show)

Fixed In Version: glusterfs-5.0
Clone Of:
Environment:
Last Closed: 2018-10-23 15:16:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Nigel Babu 2018-08-09 04:42:37 UTC
The logs say this currently

[2018-07-27 16:28:35.946588] I [MSGID: 101016] [glusterfs3.h:739:dict_to_xdr] 0-dict: key 'glusterfs.xattrop_index_gfid' is would not be sent on wire in future [Invalid argument]


That's coming from this line

"key '%s' is would not be sent on wire in future",


This should instead say

"key '%s' would not be sent on wire in future",

Comment 1 Worker Ant 2018-08-09 04:44:56 UTC
REVIEW: https://review.gluster.org/20660 (Fix a grammar error in the logs) posted (#2) for review on master by Nigel Babu

Comment 2 Worker Ant 2018-08-13 12:52:42 UTC
COMMIT: https://review.gluster.org/20660 committed in master by "Amar Tumballi" <amarts> with a commit message- Fix a grammar error in the logs

Change-Id: Ie4fe18d5094c051fa20de71f7fc841085cc6aaee
Fixes: bz#1614142
Signed-off-by: Nigel Babu <nigelb>

Comment 3 Shyamsundar 2018-10-23 15:16:35 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/


Note You need to log in before you can comment on or make changes to this bug.