Behaviour in reset_cluster and stop_deployment incosistent

[Dima Shulyak]

Part of the procedure of those two tasks is similar, reset nodes to discover state.
The difference is that in reset - we are resetting all nodes,
in stop_deployment - only unfinished.

Right now it leads to the problem with not reconfigured volumes.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/132809
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=0ff69ab5fde7bba3b2cb75a5efa20027c01781bf
Submitter: Jenkins
Branch: master

commit 0ff69ab5fde7bba3b2cb75a5efa20027c01781bf
Author: Dima Shulyak <email address hidden>
Date: Wed Nov 5 11:33:26 2014 +0200

    Refactor reset_to_discover procedure

    Added reset_to_discover method which should be used
    when node resetted to discovery state.
    - Reconfigure volumes
    - Move roles to pendings roles
    - Remove assigned ip address
    - Set pending addition

    Change-Id: I07f1d12f904e8faa76e35f00a49a978a6643eb20
    Closes-Bug: 1389572
    Related-Bug: 1273006