Comment 0 for bug 1471172

Revision history for this message
Dmitry Nikishov (nikishov-da) wrote :

MOS 6.0

HA, any configuration

Upon node removal, orchestrator doesn't clean up the cloud. This node is still present in OpenStack database and clusters.

E.g. when a controller node is deleted, user has to manually clean up following:
- delete Neutron agents associated with removed nodes from DB
- delete Nova services associated with removed nodes from DB (or else certain OSTF test will be failing)
- delete removed node from Corosync/Pacemaker cluster (or else deployment of new nodes might fail)
- delete removed node from Ceph cluster (or else ceph -s will report HEALTH_WARN for missing/offline mon)

This isn't obvious and it's not very good from UX perspective. Orchestrator should auto-clean up the cloud upon node removal.