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
We can add a confirmation question to the delete actions for OSP16.
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/
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