Comment 3 for bug 1405420

Prior to the fsm code/state changes, when a node's provision_state was DEPLOYFAIL, one could:
- PUT /v1/nodes/(node_uuid)/states/provision, with target being one of [DELETE, ACTIVE, REBUILD]
- PATCH /v1/nodes

If we changed the target_provision_state to NOSTATE when provision_state is DEPLOYFAIL, that would fix it for now. But the proposed new state machine doesn't have a NOSTATE state, so this would have to change again.

With the new state machine, if we really want the target_provision_state to be ACTIVE when provision_state is DDEPLOYFAIL, then for now, we can make code changes that get us closer to that 'final solution'.

I'm going to make a change to ironic-api, so that operations mentioned above will be allowed for nodes in provision_state=DEPLOYFAIL. It may be the case that we want to do this for most or all nodes in a *FAIL provision state, but that is something we should think about for each individual *FAIL state and this is the only *FAIL state that we have now.