yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1251525] Re: baremetal deploy helper should abort immediately if target block devices are not available

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Devananda van der Veen <1251525@xxxxxxxxxxxxxxxxxx>
Date: Wed, 05 Mar 2014 01:26:57 -0000
Reply-to: Bug 1251525 <1251525@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: ironic
       Status: In Progress => 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/1251525

Title:
  baremetal deploy helper should abort immediately if target block
  devices are not available

Status in Ironic (Bare Metal Provisioning):
  Fix Released
Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  nova-baremetal-deploy-helper does not stop a deployment even if a
  target block device or partitions are not available. In such case, the
  instance will fail to boot but nova will mark the instance as ACTIVE.
  So the user can know the failure only by the fact that the instance
  does not become accessible after a long time has passed.

  The deployment should be stopped immediately and the instance should
  be marked as ERROR.

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