Bug 762460 (GLUSTER-728) - Wrong message if tried to stop a volume which has not been started
Summary: Wrong message if tried to stop a volume which has not been started
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-728
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.0.3
Hardware: All
OS: Linux
medium
low
Target Milestone: 3.0.4
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-17 10:16 UTC by Raghavendra Bhat
Modified: 2015-03-23 01:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-03-17 10:16:11 UTC 
Suppose if we try to stop a volume which has not been started(ex:selecting infiniband option instead of ethernet while creating the volume), then it displays the message as "The following volume(s)  has been stopped". It will be better if it says "Volume you are trying to stop has  not been started at all". Because it gives the same message when we give stop volume for both successfully started volumes and non started volumes.
Comment 1 Harshavardhana 2010-03-24 00:50:39 UTC 
This is a backend "StopVolume" code change to return back sane strings to UI. Let me look into this issue.
Comment 2 Harshavardhana 2010-03-24 13:38:04 UTC 
Ok saw that such a string is shown from the webui itself. This needs to be fixed in webui stop-volume
Note You need to log in before you can comment on or make changes to this bug.