Bug 1365085

Summary: Enable accessing internals of transport through meta
Product: [Community] GlusterFS Reporter: Raghavendra G <rgowdapp>
Component: transportAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: atumball, bugs, rkavunga
Target Milestone: ---Keywords: EasyFix, Triaged
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: 2019-06-20 04:57:02 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 Raghavendra G 2016-08-08 12:21:22 UTC
Description of problem:
Currently meta prints only the protocol/client and not the transport associated with it. This bug tracks the effort to print diagnostic information of transport (whether socket is connected to remote peer, identifier, ports/address of two endpoints etc)

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Amar Tumballi 2019-06-20 04:57:02 UTC
Not picked up in a long time, closing as DEFERRED to indicate the status. Will come back to this after couple of releases.