Recovered hosts does not include "active"

[msherman64]

blazar/blazar/plugins/oshosts/host_plugin.py

Line 951 in 09cf8ee

and n.provision_state in ['available']]

Hosts only recover when "available", but "active" seems to be a permissable state

[msherman64]

If a node fails to provision, and then succeeds on a second attempt, the following happens:

1. node moves to provision state “deploy failed”
2. blazar sets node to unhealthy
3. hammer moves node from “deploy failed” -> “available”
4. User runs deploy again, node moves through provision states:
   a. “deploying”
   b. “wait-call-back”
   c. “active”

[Mark-Powers]

from Mike:

node should be reservable if:

• node is in stable, healthy state, e.g. available, active
• or transition state FROM above healthy state, e.g. available -> deploying , active -> deleting, etc

and not reservable if it’s in an unhealthy state, or transition from one
but we can probably use the target_provision_state field to make it more robust