Description of problem: The protocol client has a "connecting" state that is only ever being set and printed, not used for anything else. This should be removed. Version-Release number of selected component (if applicable): all (mainline)
REVIEW: https://review.gluster.org/20097 (client: remove the \"connecting\" state - it's not used) posted (#1) for review on master by Michael Adam
COMMIT: https://review.gluster.org/20097 committed in master by "Amar Tumballi" <amarts> with a commit message- client: remove the "connecting" state - it's not used The "connecting" state is not used anywhere really. It's only being set and printed. So remove it. Change-Id: I11fc8b0bdcda5a812d065543aa447d39957d3b38 fixes: bz#1583583 Signed-off-by: Michael Adam <obnox>
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/