yahoo-eng-team team mailing list archive

[Devananda van der Veen <1098694@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1088655 ***
    https://bugs.launchpad.net/bugs/1088655

This was fixed in https://review.openstack.org/21564

** This bug has been marked a duplicate of bug 1088655
   bare metal node partitioning does not handle errors well

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

Title:
  Baremetal driver does not set instance state to "ERROR" for all error
  cases

Status in OpenStack Compute (Nova):
  New

Bug description:
  Nova Baremetal driver does not always report an accurate "state".

  Expected:
      Upon `nova boot`, nova should report the instance state as "BUILD",
      transitioning to "ACTIVE" once instance is ready, or "ERROR" on failure.

  Actual:
      Upon `nova boot`, nova reports instance state as "ACTIVE" before instance
      is ready, and does not always set state to "ERROR" on failure.

  
  To Reproduce:
      - Set up nova/bin/nova-baremetal-deploy-helper to fail,
        e.g. by using an invalid disk image, or by raising an exception
        in method "deploy"
      - `nova boot` a new baremetal node
      - instance will be set to "ACTIVE" before its disk is copied over.
      - boot the baremetal node, causing nova-baremetal-deploy-helper
        to fail.
      - instance state remains "ACTIVE" after the error.

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