do not unregister systems from satellite/portal on server resource delete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
James Slagle |
Bug Description
We should change the behavior to not unregister systems from portal/satellite on system resource delete in Heat.
There are several reasons:
- Accidental Overcloud stack deletes. This is apparently a problem. To avoid losing the system registrations in portal/satellite we should not delete by default.
- Not deleting by default will allow us to move the RHEL registration resources under a new nested stack resource so that it no longer overrides operator specific interfaces. See https:/
- When using the server blacklist, adding a server to the blacklist causes the registration resources to be deleted due to the use of Heat conditions. In such a case, we should not unregister the system(s) from satellite/portal.
- It's trivial to delete systems from portal/satellite in large batches at a time. We should rely on operators choosing to do this manually or opt-in because this task because it's a data destructive operation in external systems to TripleO.
The old behavior can be triggered using the DeleteOnRHELUnr
Changed in tripleo: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → James Slagle (james-slagle) |
milestone: | none → pike-rc1 |
Fix proposed to branch: master /review. openstack. org/492970
Review: https:/