Bug 1479265 - Gluster Block Volume creation fails with error "Connection timeout"
Gluster Block Volume creation fails with error "Connection timeout"
Status: CLOSED NOTABUG
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: CNS-deployment (Show other bugs)
cns-3.6
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Michael Adam
Anoop
:
Depends On:
Blocks: 1479268
  Show dependency treegraph
 
Reported: 2017-08-08 04:37 EDT by Humble Chirammal
Modified: 2017-08-17 09:38 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1479268 (view as bug list)
Environment:
Last Closed: 2017-08-17 09:38:58 EDT
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 Humble Chirammal 2017-08-08 04:37:28 EDT
Description of problem:

'Gluster-block" service is running on 192.168.0.2, 192.168.0.3,192.168.0.4 and not running on 192.168.0.6. tcmu-runner, target..etc are running successfully on all 4 nodes.

However when I try to create a volume with ha 2, it fails with below error:


sh-4.2# gluster-block create vol_96d8648ebd2ff7dcb87be3a2587c6246/demovol1 ha 2 192.168.0.2,192.168.0.3,192.168.0.4,192.168.0.6 3GiB --json
{ "RESULT": "FAIL", "errCode": 255, "errMsg": "failed to configure on 192.168.0.2 : Connection timed out\nfailed to configure on 192.168.0.3 : Connection timed out\nfailed to configure on 192.168.0.4 : Connection timed out\nfailed to configure on 192.168.0.6 : Connection timed out" }

in block logs I can see below error which is expected:

[2017-08-08 08:35:36.391280] E [socket.c:2360:socket_connect_finish] 0-vol_96d8648ebd2ff7dcb87be3a2587c6246-client-1: connection to 192.168.35.3:49154 failed (Connection refused); disconnecting socket

However the block volume creation should be successful as I have 3 other nodes which are up and running with all the required services.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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