Bug 762460 (GLUSTER-728)

Summary:	Wrong message if tried to stop a volume which has not been started
Product:	[Retired] GlusterSP	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	Harshavardhana <fharshav>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.0.3	CC:	bala, cww, fharshav, platform, webteam
Target Milestone:	3.0.4
Target Release:	---
Hardware:	All
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:

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