Bug 1467510 - protocol/server: Reject the connection if the graph is not ready
protocol/server: Reject the connection if the graph is not ready
Status: POST
Product: GlusterFS
Classification: Community
Component: protocol (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mohammed Rafi KC
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-04 01:59 EDT by Mohammed Rafi KC
Modified: 2017-07-09 01:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mohammed Rafi KC 2017-07-04 01:59:01 EDT
Description of problem:

We are accepting new connections even though the graph is not ready.


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


How reproducible:


Steps to Reproduce:
1. Create a volume and start it
2. as soon as the volume is started, start the client also.
3. the connections will be accepted, even when there is no child up event

Actual results:

it just logs and continue

Expected results:

it should fail

Additional info:
Comment 1 Worker Ant 2017-07-04 01:59:22 EDT
REVIEW: https://review.gluster.org/17686 (protocol/server: reject the connection if graph is not ready) posted (#1) for review on master by mohammed rafi  kc (rkavunga@redhat.com)
Comment 2 Worker Ant 2017-07-09 01:24:52 EDT
REVIEW: https://review.gluster.org/17686 (protocol/server: reject the connection if graph is not ready) posted (#2) for review on master by Atin Mukherjee (amukherj@redhat.com)

Note You need to log in before you can comment on or make changes to this bug.