Bug 763748 (GLUSTER-2016)

Summary:	"start volume" reports success when volume hasn't actually been started
Product:	[Community] GlusterFS	Reporter:	Vikas Gorur <vikas>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	gluster-bugs, vijay, vraman
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:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vikas Gorur 2010-10-26 21:59:44 UTC

This happens in many cases - one specific example is:

If the glusterfs-rdma rpm is not installed and the user tries to start a volume of transport type rdma, the "brick" glusterfs processes do not start. Despite this, the CLI reports "volume start has been successful". If you try to mount this volume all accesses simply hang.

The UI should not make false statements. It should only report success when it can verify that all the bricks have started and all the NFS servers have started.

Comment 1 Vijay Bellur 2010-10-28 14:32:30 UTC

This will be addressed when 1203 is fixed.

*** This bug has been marked as a duplicate of bug 1203 ***