Different instance_name_template config in controller node and compute node will lead to VM not be deleted actually
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Low
|
Unassigned |
Bug Description
If we config instance_
The reason of the issue are:
When boot instance, instance's name generated on controller node using controller's instance_
But When delete instance, instance's name do not pass from controller node to compute node, the instance's name is generated on compute node using compute's instance_
The nova should use instance_
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → jichencom (jichenjc) |
Changed in nova: | |
importance: | Undecided → Wishlist |
I analyzed this problem and looks to me compute/manager.py and virt/*.py highly depends on the instance['name']
which means it's not easy to transfer instance_name from api to compute node unless we not only transfer uuid of the instance but also transfer the instance name , it's complicated and not worthy
Also, if we think there are multiple nova-api service with different instance_ name_template, it also can lead to problem and modification on compute layer won't help
Is there a way to do offline check to help admin on this? would think a healthy checker will be much helpful