Bug 763933 (GLUSTER-2201)
| Summary: | Can't stop a Gluster volume via a script - | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Craig Carl <craig> |
| Component: | cli | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.1.1 | CC: | aavati, craig, eco, gluster-bugs, jacob, 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
Anand Avati
2010-12-07 22:56:02 UTC
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. Perfect, thanks. |