Bug 763933 – Can't stop a Gluster volume via a script -

Bug 763933 - (GLUSTER-2201) Can't stop a Gluster volume via a script -

Summary:	Can't stop a Gluster volume via a script -

Status:	CLOSED NOTABUG

Aliases:	GLUSTER-2201

Product:	GlusterFS
Classification:	Community
Component:	cli (Show other bugs)
Sub Component:
Version:	3.1.1
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Amar Tumballi
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-12-07 20:37 EST by Craig Carl
Modified:	2013-12-18 19:05 EST (History)
CC List:	6 users (show)

See Also:
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:	---

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

Groups: None (edit)

Description Anand Avati 2010-12-07 17:56:02 EST

gluster --mode=script volume stop _volname_ [force]. That will skip asking interacting questions.

Avati

Comment 1 Craig Carl 2010-12-07 20:37:38 EST

All - 
   The Gluster volume stop command is interactive, it requires answering a "are you sure?" question. As a result the command is not readily script-able. The "force" option does not eliminate this requirement. 

   Eco was able to get around the problem with "yes | gluster volume stop gvol1" but this is an obvious kludge. 

   I would suggest that every interactive command include a "y" or "yes" switch that assumes yes to every prompt, this would be consistent with other *nix tools.

Comment 2 Craig Carl 2010-12-07 21:21:49 EST

Perfect, thanks.

Note You need to log in before you can comment on or make changes to this bug.