How to protect individual overcloud nodes from accidental deletion by OpenStack Director in Red Hat OpenStack Platform 13
Issue
How to protect individual nodes from accidental deletion by OpenStack Director in Red Hat OpenStack Platform 13?
Administrators might involuntarily instruct OpenStack Director to delete or replace the wrong overcloud node.
For example:
-
By providing a wrong UUID to the
openstack overcloud node delete <UUID>
command -
Or by incorrectly using the
RemovalPolicies
feature: https://access.redhat.com/solutions/4232971
In the above scenarios, how can administrators make sure that OpenStack Director cannot power down or reprovision specific baremetal machines?
Environment
Red Hat OpenStack Platform 13
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.