protocol/client: Maintain connection to brick status

Problem:
The current version of the code depends on the non-zero-port information to
propagate ping event from brick to parent layers. But as and when connection
succeeds, port is set to zero in rpc layer.So ping event is never propagated to
parent layers. Halo doesn't work without this.

Fix:
Remember the status of connection in 'private' structure and use that to decide
to propagate ping event to parent xlator.

fixes: bz#1797934
Change-Id: Ia578ba9fb3813953d2068dbba5c982ab27cc3429
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

0 files changed, 0 insertions, 0 deletions