Delete compute service when deleting compute node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Fuel Documentation Team | ||
6.1.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
7.0.x |
Confirmed
|
High
|
Fuel Documentation Team | ||
8.0.x |
Confirmed
|
Wishlist
|
Fuel Python (Deprecated) |
Bug Description
When we delete the compute node with help of Fuel, it still leaves as the compute service in OpenStack. It becomes marked offline forever or until the administrator deletes it from the database manually.
There are two ways of workaround:
1. There if the API call in Nova (Change-Id: I655a7f818bb59c
2. We may clean the database with the next steps:
mysql -u root -p
use nova;
delete from compute_node_stats where compute_
delete from compute_nodes where service_id=(select id from services where host='hostname');
delete from services where host='hostname';
Changed in fuel: | |
importance: | Undecided → Medium |
milestone: | none → 6.0 |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Fuel Python Team (fuel-python) |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
tags: | added: feature |
Changed in fuel: | |
milestone: | 6.1 → next |
Changed in fuel: | |
milestone: | next → 7.0 |
tags: |
added: release-notes removed: feature |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
tags: | added: life-cycle-management |
Does not break deployment. Requires release-notes. Moved to 8.0.