yahoo-eng-team team mailing list archive

[Joe Gordon <1184473@xxxxxxxxxxxxxxxxxx>]

since we are in the process of deprecating nova baremetal, I don't think
we want to fix this.

** Also affects: ironic
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: Triaged => Opinion

-- 
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/1184473

Title:
  no way to resume a baremetal deployment after restarting n-cpu

Status in OpenStack Bare Metal Provisioning Service (Ironic):
  New
Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  If the nova-compute process is terminated while the baremetal PXE
  driver is waiting inside activate_node() for baremetal-deploy-helper
  to finish copying the image, there is no way to resume the deployment.
  Currently, recovery from this situation requires that the instance and
  the baremetal node be deleted, possible manual editing of the nova
  database, and waiting for the compute_manager to trigger
  update_available_resource and reap the dead compute_node.

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