Bug 868801

Summary: gluster volume creation says 'success' but volume does not exist on any of the peers
Product: [Community] GlusterFS Reporter: Rachana Patel <racpatel>
Component: glusterdAssignee: Krutika Dhananjay <kdhananj>
Status: CLOSED WORKSFORME QA Contact: amainkar
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: amarts, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-14 02:07:15 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Rachana Patel 2012-10-22 03:51:24 EDT
Description of problem:
gluster volume creation says 'success' but volume does not exist on any of the peers

Version-Release number of selected component (if applicable):
glusterfs 3git built on Oct 22 2012 09:46:02

[root@Rhsgit2 glusterfs]# git log
commit cf63a76ca03240eb617ca5bd2aa9b3f7abe7b6a4
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Oct 20 19:30:06 2012 +0200

How reproducible:


Steps to Reproduce:
1. start glusterd on all peers.
2. verify that peers are connected using 'gluster p s' 
3. execute volume creation from one server

[root@rhsgit1 glusterfs]# gluster volume create san_22 10.70.35.107:/home/san_22_1 10.70.35.107:/home/san_22_2 10.70.35.71:/home/san_22_2  10.70.35.71:/home/san_22_1
volume create: san_22: success: please start the volume to access data

4. start volume
[root@rhsgit1 glusterfs]# gluster volume start san_22
volume start: san_22: failed: Volume san_22 does not exist

5. verify volume info on all peer
[root@rhsgit1 glusterfs]# gluster volume info
 
volume is not present
  
Actual results:
gluster volume creation says 'success' but volume does not exist on any of the peers

Expected results:
If volume creation is failed then it should not report creation successful.

Additional info:
Comment 1 Amar Tumballi 2013-02-26 05:43:25 EST
don't think its valid anymore... but needs a round of validation before closing.
Comment 2 Krutika Dhananjay 2013-03-14 02:07:15 EDT
Tried reproducing the bug, not been able to hit it, hence closing the bug.