Bug 763748 (GLUSTER-2016) - "start volume" reports success when volume hasn't actually been started
Summary: "start volume" reports success when volume hasn't actually been started
Keywords:
Status: CLOSED DUPLICATE of bug 762935
Alias: GLUSTER-2016
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.1.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 21:59 UTC by Vikas Gorur
Modified: 2013-12-19 00:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.