test "partially_deployed_unlock" fails if compute nodes deployed before

[ElenaRossokhina]

Detailed bug description:
Found on CI: https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.unlock_settings_tab_states/10/testReport/(root)/partially_deployed_unlock/
Steps to reproduce:
Revert snapshot ready_with_3_slaves
Create a new env
Add controller and 2 computes
Provision nodes without deploy
Select some nodes (not all) and deploy them
Expected results:
Partial deploy passed
Actual result:
Deploy fails.
Reproducibility:
infrequently

According to test, nodes with ids 1 and 2 should be deployed. If both of them are computes, such config will fail on deploy

Found on 9.0 + snapshot#64
CUSTOM_VERSION=snapshot #64
MAGNET_LINK=magnet:?xt=urn:btih:bfec808dd71ff42c5613a3527733d9012bb1fabc&dn=MirantisOpenStack-9.0.iso&tr=http%3A%2F%2Ftracker01-bud.infra.mirantis.net%3A8080%2Fannounce&tr=http%3A%2F%2Ftracker01-scc.infra.mirantis.net%3A8080%2Fannounce&tr=http%3A%2F%2Ftracker01-msk.infra.mirantis.net%3A8080%2Fannounce&ws=http%3A%2F%2Fvault.infra.mirantis.net%2FMirantisOpenStack-9.0.iso
FUEL_QA_COMMIT=ef8921352dd9a500e8609c05cc17956d3b95455c
UBUNTU_MIRROR_ID=ubuntu-2016-07-27-174626
CENTOS_MIRROR_ID=centos-7.2.1511-2016-05-31-083834
MOS_UBUNTU_MIRROR_ID=9.0-2016-07-28-170322
MOS_CENTOS_OS_MIRROR_ID=os-2016-06-23-135731
MOS_CENTOS_PROPOSED_MIRROR_ID=proposed-2016-07-28-170322
MOS_CENTOS_UPDATES_MIRROR_ID=updates-2016-06-23-135916
MOS_CENTOS_HOLDBACK_MIRROR_ID=holdback-2016-06-23-140047
MOS_CENTOS_HOTFIX_MIRROR_ID=hotfix-2016-07-18-162958
MOS_CENTOS_SECURITY_MIRROR_ID=security-2016-06-23-140002

diagnostic snapshot https://drive.google.com/open?id=0B2ag_Bf-ShtTX0QwRWNFaUVXWjA

[Sergey Shevorakov (sshevorakov)]

Moving to High since it fails one Swarm test case.

[Nastya Urlapova (aurlapova)]

@Elena, issue with deployment should fix the sustaining team.

[Dmitry Pyzhov (dpyzhov)]

Compute node deployment will fail without working controller. Single node deployment is advanced feature and we don't have extra safety checks for it. So this is intended behaviour. Please update your tests.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/355418
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=2449f17eee608e73de71b96c79c3de0cae446397
Submitter: Jenkins
Branch: master

commit 2449f17eee608e73de71b96c79c3de0cae446397
Author: Alexander Kurenyshev <email address hidden>
Date: Mon Aug 15 14:33:26 2016 +0300

    Improve node selection for partially deploy

    We have a hardcoded values for a selected nodes.
    Sometimes this could lead test fail when we try to
    deploy both computes instead of a controller and
    compute.
    This fix adds a smart nodes selection by nodes
    and their roles

    Change-Id: Icde591cd47afb6a3e5574aea9267ef3543b7c158
    Closes-Bug:1607809

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/355914

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/355914
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=292b8e2efd1bd0f2eb6703b316b79ce5c40a63da
Submitter: Jenkins
Branch: stable/mitaka

commit 292b8e2efd1bd0f2eb6703b316b79ce5c40a63da
Author: Alexander Kurenyshev <email address hidden>
Date: Mon Aug 15 14:33:26 2016 +0300

    Improve node selection for partially deploy

    We have a hardcoded values for a selected nodes.
    Sometimes this could lead test fail when we try to
    deploy both computes instead of a controller and
    compute.
    This fix adds a smart nodes selection by nodes
    and their roles

    Change-Id: Icde591cd47afb6a3e5574aea9267ef3543b7c158
    Closes-Bug:1607809
    (cherry picked from commit 2449f17eee608e73de71b96c79c3de0cae446397)

[Tatyana Kuterina (tkuterina)]

Verified on 9.1 snapshot #153

FUEL_QA_COMMIT=b525749639a1880f7663bee0513cc541e3a3c7cf