Description of problem: Presently there is no mechanism by which nodes which are being scaled-down / deleted can run any automated clean up; they simply get shutoff and removed from the pool. Examples of house-keeping tasks that may be desired include: Unsubscribing themselves from subscription manager, thus freeing resources. Cleaning up service entries for compute nodes. There is a desire for these functions and as such it would be helpful for work to be done to allow such hooks.
Upstream blueprint: https://blueprints.launchpad.net/tripleo/+spec/scale-down-tasks
Since https://bugzilla.redhat.com/show_bug.cgi?id=1544441 has been verified, this one is also verified de fact: the feature verified in that other BZ uses this new framework for the un-subscription during scale-down. Test protocol: - deploy Director with a couple of Overcloud nodes, registered against RHSM - remove one of the overcloud node - check that this node has been un-subscribed from RHSM
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