Ironic Nova driver makes two calls to delete a node
Bug #1436568 reported by
Josh Gachnang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Lucas Alvares Gomes | ||
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Lucas Alvares Gomes |
Bug Description
When deleting an instance in Nova, it sets the provision state to DELETED and then when that completes (node is in CLEANING, CLEANFAIL, or NOSTATE/AVAILABLE), it makes another call to remove the instance UUID. The instance UUID should be cleared out when Ironic clears out node.instance_info, and Nova should delete the instance as soon as the node is one of the states above.
Changed in ironic: | |
assignee: | nobody → Josh Gachnang (joshnang) |
Changed in nova: | |
assignee: | nobody → Josh Gachnang (joshnang) |
tags: | added: ironic |
Changed in nova: | |
importance: | Undecided → Low |
Changed in ironic: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
importance: | Low → Medium |
Changed in ironic: | |
milestone: | none → 4.0.0 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-3 → 12.0.0 |
To post a comment you must log in.
Hi Josh,
I think the problem here is that Nova relies on finding a node with that instance_uuid when waiting the provision state after marking the node to be deleted [1], if that bit just handled NodeNotFound and gracefully exit that loop (assuming Ironic had cleaned the instance_uuid) it wouldn't be a problem.
I'm going to put up a patch to do it.
[1] https:/ /github. com/openstack/ nova/blob/ master/ nova/virt/ ironic/ driver. py#L809