Bug 1584864 - sometime messages
Summary: sometime messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 20:13 UTC by Levi Baber
Modified: 2018-10-23 15:10 UTC (History)
1 user (show)

Fixed In Version: glusterfs-5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-23 15:10:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Levi Baber 2018-05-31 20:13:57 UTC
Description of problem:

Several glusterd processes display a message when another transaction is in process. These are worded as "Another transaction is in progress...Please try again after sometime."

This is an incorrect usage of "sometime" and it should be "some time".


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


How reproducible:
Always

Steps to Reproduce:
1. Run a command like gluster volume quota and then immediately rerun before the previous transaction has completed.

Actual results:
"Another transaction is in progress...Please try again after sometime."

Expected results:
"Another transaction is in progress...Please try again after some time."

Additional info:
N/A

Comment 1 Worker Ant 2018-05-31 20:20:38 UTC
REVIEW: https://review.gluster.org/20115 (changed 'sometime' messsages to 'some time') posted (#1) for review on master by

Comment 2 Worker Ant 2018-06-01 23:44:53 UTC
COMMIT: https://review.gluster.org/20115 committed in master by "Vijay Bellur" <vbellur> with a commit message- changed 'sometime' messsages to 'some time'

Change-Id: I0936229fc84c011db7791218bb566c971fdea174
fixes: bz#1584864
Signed-off-by: Levi Baber <baber>

Comment 3 Shyamsundar 2018-10-23 15:10:44 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.