Bug 1593057 - Prevent overcloud node deletion/replacement by OpenStack Director or query user if he/she really really wants to delete/replace a node
Summary: Prevent overcloud node deletion/replacement by OpenStack Director or query us...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: rc
: 16.0 (Train on RHEL 8.1)
Assignee: Alex Schultz
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-20 00:41 UTC by Andreas Karis
Modified: 2022-08-09 09:38 UTC (History)
16 users (show)

Fixed In Version: python-tripleoclient-12.3.1-0.20191115200343.315f6d4.el8ost
Doc Type: Enhancement
Doc Text:
With this enhancement, overcloud node deletion requires user confirmation before the action will be performed to reduce the likelihood that the action is performed unintentionally. The `openstack overcloud node delete <node>` command requires a Y/n confirmation before the action executes. You can bypass this by adding `--yes` to the command line.
Clone Of:
Environment:
Last Closed: 2020-02-06 14:37:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 660169 0 'None' MERGED Add a user confirmation to node delete 2020-11-25 10:51:52 UTC
Red Hat Issue Tracker OSP-9185 0 None None None 2022-08-09 09:38:34 UTC
Red Hat Product Errata RHEA-2020:0283 0 None None None 2020-02-06 14:39:38 UTC

Description Andreas Karis 2018-06-20 00:41:17 UTC 
Hi,

In OSP 7,8,9,10, we regularly ran and run into bugs where OSP Director will delete or replace nova nodes. May this be bugs in the product, user mistakes or both at the same time:, e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=1592246
https://bugzilla.redhat.com/show_bug.cgi?id=1544088

For whatever reason these node deletions occur, we have to be able to lock down nodes, or at least we need to prompt an admin if he/she really really wants to delete a node. And this whenever a node is to be replaced or deleted.

Thanks,

Andreas
Comment 2 Alex Schultz 2019-05-14 17:14:42 UTC 
We can add a confirmation question to the delete actions for OSP16.
Comment 8 David Rosenfeld 2020-02-03 16:01:44 UTC 
Originally in OSP 16 automation with a scale down stage was hanging for hours because it was not responding to the new confirmation message. After automation was updated to respond to confirmation the hang went away: Ex: of a passing job:

https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/df/view/rfe/job/DFG-df-rfe-16-virsh-3cont_3comp_3ceph-blacklist-1compute-1control-compute-replacement/
Comment 10 errata-xmlrpc 2020-02-06 14:37:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283
Note You need to log in before you can comment on or make changes to this bug.