Ironic. Failed to delete node. Node is locked by host.

Solution Verified - Updated -

Issue

Originally it was impossible to delete the overcloud stack: delete command failed with the following error:

[overcloud.computeHCI]: DELETE_FAILED ResourceInError: resources.ComputeHCI.resources[2].resources.Compute.HCI: Went to status ERROR due to "Server compute03 delete failed: (500) Build of instance 11111111-2222-3333-4444-555555555555 aborted: Instance 11111111-2222-3333-4444-555555555555 provis
[overcloud]: DELETE_FAILED Resource DELETE failed: ResourceInError: resources.ComputeHCI.resources[2].resources.Compute.HCI: Went to status ERROR due to "Server compute03 delete failed: (500) Build of instance 11111111-2222-3333-4444-555555555555 aborted: Instance 11111111-2222-3333-

  Stack overcloud DELETE_FAILED

The output of openstack baremetal node list command stated that one node was powered on and also was in deploying state. It was impossible to change provisioning state, maintenance mode, or simple delete this node. A same output was returned for every request by ironic:

Node 5555453a-777d-4222-a0d1-333d44460ab7 is locked by host director.localhost, please retry after the current operation is completed. (HTTP 409)

Environment

This issue was faced in Red Hat OpenStack 13 environment. It is possible to run into it in other releases.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In