Orchestrator doesn't clean deleted node from the cloud upon node removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Matthew Mosesohn | ||
6.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
6.1.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
7.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
Mitaka |
Won't Fix
|
High
|
Fuel Library (Deprecated) |
Bug Description
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)
- delete appropriate devices from swift rings
This isn't obvious and it's not very good from UX perspective. Orchestrator should auto-clean up the cloud upon node removal.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
milestone: | none → 7.0 |
importance: | Undecided → Medium |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
tags: | added: docs |
description: | updated |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
no longer affects: | fuel/8.0.x |
tags: | added: area-library |
Changed in fuel: | |
assignee: | Alex Schultz (alex-schultz) → nobody |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
status: | Triaged → New |
no longer affects: | fuel/future |
no longer affects: | fuel/future |
Changed in fuel: | |
milestone: | 10.0 → next |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/future |
tags: | added: swarm-blocker |
tags: | removed: swarm-blocker |
no longer affects: | fuel/newton |
tags: |
added: release-notes-done removed: release-notes |
At least "delete removed node from Corosync/Pacemaker cluster" was addressed in the 6.1 scope. I'm setting the status as incomplete for the 6.1 and later milestones as it requires QA confirmation