Red Hat Bugzilla – Bug 763748
"start volume" reports success when volume hasn't actually been started
Last modified: 2013-12-18 19:05:48 EST
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.
This will be addressed when 1203 is fixed.
*** This bug has been marked as a duplicate of bug 1203 ***