yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1184473] Re: no way to resume a baremetal deployment after restarting n-cpu

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Jay Faulkner <1184473@xxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Sep 2016 15:44:07 -0000
Reply-to: Bug 1184473 <1184473@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug has been incomplete for 2 years. Closing as invalid.

** Changed in: ironic
       Status: Incomplete => Invalid

-- 
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 Ironic:
  Invalid
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