Bug 1583583

Summary:	"connecting" state in protocol client is useless
Product:	[Community] GlusterFS	Reporter:	Michael Adam <madam>
Component:	protocol	Assignee:	Michael Adam <madam>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	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:10:12 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 Michael Adam 2018-05-29 09:59:58 UTC

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)

Comment 1 Worker Ant 2018-05-29 10:01:33 UTC

REVIEW: https://review.gluster.org/20097 (client: remove the \"connecting\" state - it's not used) posted (#1) for review on master by Michael Adam

Comment 2 Worker Ant 2018-06-21 05:37:35 UTC

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>

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