Bug 763653 (GLUSTER-1921)

Summary:	Cli still asks for wrong confirmation even if the volume is stopped
Product:	[Community] GlusterFS	Reporter:	Harshavardhana <fharshav>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	cww, gluster-bugs, vijay, vraman
Target Milestone:	---
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:
Embargoed:

Description Harshavardhana 2010-10-11 23:54:11 UTC

[root@platform test1]# gluster volume info test1

Volume Name: test1
Type: Distribute
Status: Stopped
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.1.10.202:/storage
[root@platform test1]# gluster volume stop test1
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume test1 has been unsuccessful
[root@platform test1]# 

This can be done better by making cli say its already stopped since it already knows it is stopped.

Comment 1 Vijay Bellur 2010-10-28 08:56:15 UTC


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