Bug 984881 - Gluster volume create fails
Gluster volume create fails
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs (Show other bugs)
2.1
Unspecified Unspecified
medium Severity high
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
glusterd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-16 05:34 EDT by senaik
Modified: 2015-12-03 12:19 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-03 12:19:34 EST
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 senaik 2013-07-16 05:34:44 EDT
Description of problem:
========================= 
Gluster volume create failing with error : Staging failed on one node and Host not connected on another node 

Version-Release number of selected component (if applicable):
===========================================================
3.4.0.12rhs.beta4-1.el6rhs.x86_64

How reproducible:
================

Steps to Reproduce:
=================

1.Create a 2x2 distributed replicated volume 

gluster volume create vol5 replica 2 10.70.34.85:/rhs/brick1/xyz1 10.70.34.105:/rhs/brick1/xyz2 10.70.34.85:/rhs/brick1/xyz3 10.70.34.86:/rhs/brick1/xyz4
volume create: vol5: failed: Staging failed on 10.70.34.85. Error: Host 10.70.34.86 not connected

3.Check gluster peer status from all nodes 

Node1 : 
------- 
[root@fillmore ~]# gluster peer status
Number of Peers: 2

Hostname: 10.70.34.85
Uuid: f7f22764-80ee-45e9-a9ef-ba07f1e6348e
State: Peer in Cluster (Connected)

Hostname: 10.70.34.86
Uuid: 1d1c763f-c635-49a3-93ae-d7e7e17b58eb
State: Peer in Cluster (Connected)

Node 2 : 
-------- 
[root@boost ~]# gluster peer status
Number of Peers: 2

Hostname: 10.70.34.86
Uuid: 1d1c763f-c635-49a3-93ae-d7e7e17b58eb
State: Peer in Cluster (Disconnected) -------------> status is disconnected 

Hostname: 10.70.34.105
Uuid: 386a8f33-a2ca-4366-88a6-60407d550b16
State: Peer in Cluster (Connected)

Node 3 : 
------- 
 gluster peer status
Number of Peers: 2

Hostname: 10.70.34.105
Uuid: 386a8f33-a2ca-4366-88a6-60407d550b16
State: Peer in Cluster (Connected)

Hostname: 10.70.34.85
Uuid: f7f22764-80ee-45e9-a9ef-ba07f1e6348e
State: Peer in Cluster (Connected)

Glusterd status from the disconnected node : 
------------------------------------------- 
[root@jay brick1]# service glusterd status
glusterd (pid  1723) is running...


Actions performed on the nodes before creating volume : 
----------------------------------------------------- 

1) rebooted 10.70.34.85 while rebalance is in progress 

2) rebooted 10.70.34.86 while rebalance is in progress 

Actual results:
============== 
Volume create is failing 

Expected results:
================== 
Volume create should not fail

Additional info:
Comment 4 Vivek Agarwal 2015-12-03 12:19:34 EST
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.

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