add_node_after_upgrade test tries to provision cluster after upgrade without reset

[Andrey Sledzinskiy]

https://github.com/stackforge/fuel-qa/blob/master/fuelweb_test/tests/tests_upgrade/test_upgrade.py#L744
https://github.com/stackforge/fuel-qa/blob/master/fuelweb_test/tests/tests_upgrade/test_upgrade.py#L975

In those two tests we provision deployed cluster again. It's not right because we have deployed openstack and without proper erasing it can bring a lot of errors.

We should just re-deploy cluster after adding new nodes

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/230331
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=78f5400892f9acb61035c789733a5fc3d3ec0c08
Submitter: Jenkins
Branch: master

commit 78f5400892f9acb61035c789733a5fc3d3ec0c08
Author: vgorin <email address hidden>
Date: Fri Oct 2 12:21:55 2015 +0300

    Delete provision of all cluster after adding node to it.

    Changes belong to add_node_after_upgrade tests.

    Change-Id: Ic8e941c3ce7d54e6b742d93b58cd4d5da1ebe7e4
    Closes-Bug: #1497327