Description of problem: When running "instack-ironic-deployment --discover-nodes", you get an error after the 1st succesful node that's discovered and the command exits. Here is an example of running discovery on 7 bare metal nodes: [stack@puma01 ~]$ instack-ironic-deployment --discover-nodes Preparing for deployment... Discovering nodes. Sending node ID dd415b24-9b98-4df1-a580-7511f8a6a419 to discoverd for discovery ... DONE. Sending node ID 2eb49204-0707-4063-a611-8209f09ab2a5 to discoverd for discovery ... DONE. Sending node ID afe53894-1827-4bd7-89ab-36c70f9062dd to discoverd for discovery ... DONE. Sending node ID 637efe5b-5dff-4528-8776-bd121fd6dc73 to discoverd for discovery ... DONE. Sending node ID 11a78e0c-752f-4714-9033-e930082741db to discoverd for discovery ... DONE. Sending node ID 1c8f25d9-49e4-4d1c-9db8-090d208ddef3 to discoverd for discovery ... DONE. Sending node ID f98ed526-c157-46f7-afd9-c3e21eacbf00 to discoverd for discovery ... DONE. Polling discoverd for discovery results ... Result for node dd415b24-9b98-4df1-a580-7511f8a6a419 is ... DISCOVERED. Node dd415b24-9b98-4df1-a580-7511f8a6a419 is locked by host puma01.scl.lab.tlv.redhat.com, please retry after the current operation is completed. (HTTP 409) You can check that all discoveries completed without errors despite the unsuccessful termination of the above command. Use "openstack baremetal introspection status $node_id -f value -c finished" and "openstack baremetal introspection status $node_id -f value -c error" to see that all discoveries finished and there were no errors. Version-Release number of selected component (if applicable): openstack-ironic-discoverd-1.1.0-0.99.20150512.1639git.el7.centos.noarch openstack-ironic-common-2015.1-dev684.el7.centos.noarch openstack-ironic-conductor-2015.1-dev684.el7.centos.noarch python-ironic-discoverd-1.1.0-0.99.20150512.1639git.el7.centos.noarch openstack-ironic-api-2015.1-dev684.el7.centos.noarch python-ironicclient-0.5.1-post7.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Register bare metal nodes 2. Discover with "instack-ironic-deployment --discover-nodes" Actual results: You always get this error that the node is locked by the host. Does it mean that my own host is locking the resources for itself? Expected results: All introspections should end successfully, and all nodes should be listed as DISCOVERED.
This has been fixed so the bug can be closed.
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.