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

Bug #1098694 reported by Tim Miller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

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.

Tags: baremetal
aeva black (tenbrae)
tags: added: baremetal
Revision history for this message
aeva black (tenbrae) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.