yahoo-eng-team team mailing list archive

[Jim Rollenhagen <jim@xxxxxxxxxxxxxxxxxx>]

This has been fixed for a while; we only expose resources available to a
node in AVAILABLE/NONE provision state and with no instance uuid:
https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L301-L318

** Changed in: nova
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1326639

Title:
  Ironic nova driver fails to setup initial state correctly

Status in Ironic:
  Invalid
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  2014-06-05 04:04:54.552 28915 ERROR ironic.nova.virt.ironic.driver
  [req-66403d15-5f7e-4a59-8d3d-ba9d6e654fb5 None] Failed to request
  Ironic to provision instance ef3421ef-e7b3-4203-811c-dad052b9badf: RPC
  do_node_deploy called for cfa5c267-3a7c-4973-bdcf-80a139a947ea, but
  provision state is already deploy failed. (HTTP 500)

  
  This happened because the node wasn't 'properly' cleaned after the last instance_uuid was removed from it. Seems to me that the ironic nova driver should not make any assumptions - just its instance_uuid atomically, and then reset all the state, and finally proceed to set the state it wants for deployment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1326639/+subscriptions