Bug 1283805 - pcs cluster destroy does not warn or prompt for conformation before destroying cluster
pcs cluster destroy does not warn or prompt for conformation before destroyin...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs (Show other bugs)
7.3
Unspecified Linux
medium Severity unspecified
: rc
: ---
Assigned To: Tomas Jelinek
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-19 19:01 EST by Sam McLeod
Modified: 2017-07-21 07:06 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam McLeod 2015-11-19 19:01:25 EST
Description of problem:

pcs cluster destroy immediately destroys cluster configuration without warning.

As the action is highly distructive there should probably be a conformation prompt or the requirement to use a conformation flag such as --force.

Version-Release number of selected component (if applicable):

0.9.137

How reproducible:

Every time

Steps to Reproduce:

dev-samm-01:~ # pcs cluster destroy
Shutting down pacemaker/corosync services...
Redirecting to /bin/systemctl stop  pacemaker.service
Redirecting to /bin/systemctl stop  corosync.service
Killing any remaining services...
Removing all cluster configuration files...

Actual results:

All cluster configuration, state and data immediately destroyed

Expected results:

A warning or conformation prompt, for example:

dev-samm-01:~ # pcs cluster destroy

WARNING - this is will stop and remove cluster configuration, state and data!

Do you wish to proceed? (Y/n)

dev-samm-01:~ # Y
Shutting down pacemaker/corosync services...
Redirecting to /bin/systemctl stop  pacemaker.service
Redirecting to /bin/systemctl stop  corosync.service
Killing any remaining services...
Removing all cluster configuration files...

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