When Ironic returns a 409 result, it could be that the node is locked while another operation is being performed, like checking power status. This error shouldn't be fatal, and we should retry a few times to see if the lock gets released. baremetal-operator already does this, and v0.1.7 of terraform-provider-ironic will as well.

When the installer encounters this, it current fails installation with an error like below:


level=debug msg="2019/08/20 14:12:52 [DEBUG] module.masters.ironic_node_v1.openshift-master-host[1]: apply errored, but we're indicating that via the Error pointer rather than returning it: could not make node available: Expected HTTP response code [202] when accessing [PUT http://172.22.0.2:6385/v1/nodes/9820eba5-5ae0-44d3-b536-25f46bf3e8c9/states/provision], but got 409 instead"
level=debug msg="{\"error_message\": \"{\\\"debuginfo\\\": null, \\\"faultcode\\\": \\\"Client\\\", \\\"faultstring\\\": \\\"Node 9820eba5-5ae0-44d3-b536-25f46bf3e8c9 is locked by host localhost.localdomain, please retry after the current operation is completed.\\\"}\"}"
level=debug msg="2019/08/20 14:12:52 [ERROR] module.masters: eval: *terraform.EvalApplyPost, err: could not make node available: Expected HTTP response code [202] when accessing [PUT http://172.22.0.2:6385/v1/nodes/9820eba5-5ae0-44d3-b536-25f46bf3e8c9/states/provision], but got 409 instead"
level=debug msg="{\"error_message\": \"{\\\"debuginfo\\\": null, \\\"faultcode\\\": \\\"Client\\\", \\\"faultstring\\\": \\\"Node 9820eba5-5ae0-44d3-b536-25f46bf3e8c9 is locked by host localhost.localdomain, please retry after the current operation is completed.\\\"}\"}"`