Baremetal driver does not set instance state to "ERROR" for all error cases
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/
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-
to fail.
- instance state remains "ACTIVE" after the error.
tags: | added: baremetal |
This was fixed in https:/ /review. openstack. org/21564