Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1797934

Summary:	Client should propagate ping event from brick
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-05 12:13:41 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 Pranith Kumar K 2020-02-04 09:21:11 UTC

Description of problem:
The current version of the code depends on the non-zero-port information to propagate ping event but as and when connection succeeds, port is set to zero in rpc layer. So ping event is never propagated to parent layers.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2020-02-04 10:26:53 UTC

REVIEW: https://review.gluster.org/24093 (protocol/client: Maintain connection to brick status) posted (#1) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2020-02-05 12:13:41 UTC

REVIEW: https://review.gluster.org/24093 (protocol/client: Maintain connection to brick status) merged (#3) on master by Pranith Kumar Karampuri