[RFE] Support abort for nodes in deploy_wait

[Tan Lin]

when I use Ironic standalone and input a wrong ramdisk, nodes will stuck on wait_for_call state. I know `delete` action can solve this problem, but it will delete the instance_info too. I just want to change the wrong parameters and call `active` to build it again. Abort action sounds a better solution for this case.

So will extend 'abort' action to deploy_wait state

[Tan Lin (tan-lin-good)]

Made a mistake, sorry. Notice that instance_info was deleted in conductor/manager: _do_node_tear_down.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/244070

[Tan Lin (tan-lin-good)]

One more issue raised:
when used with Nova, if abort deploy-wait to deploy-failed, nova will send a request to destroy the instance which means equal to `delete` action

[Sam Betts (sambetts)]

Myself and Lucas agree that this is something we want to support, however we believe this will require an update to state machine and therefore should be supported by a spec.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ruby Loo (<email address hidden>) on branch: master
Review: https://review.openstack.org/244070
Reason: Tan Lin is no longer working on ironic, and this patch hasn't been updated since Jan 2016, so I'm abandoning it. It can be restored if someone wants to continue working on it.

[Ruby Loo (rloo)]

Lin Tan is no longer working on ironic.

[Michael Turek (mjturek)]

This wishlist bug has been open more than a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. This bug can be reopened (set back to "New") if someone decides to work on this.