When there is a deployment of custom graph only on master node, deployment fails with 'Could not find any hosts in discovery data provided'

[Alexandr Kostrikov]

At SWARM run [0] test with scenario fails:

        Scenario:
            1. Revert snapshot 'pre_provision_ubuntu_slaves_3'
            3. Create cluster
            3. Upload 'master_node' tasks
            4. Run 'master_node' tasks
            5. Verify that tasks are executed in correct order
            6. Create snapshot

with error
Task 'deployment' has incorrect status. error != ready, 'Deployment has failed. Method task_deploy. #<RuntimeError: Could not find any hosts in discovery data provided>
.
Inspect Astute logs for the details

Additional information:
That is regression. Test has been passing for a long time and started to fail recently (1-2 days)

[0] https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.custom_graph/19/testReport/(root)/master_node_tasks/master_node_tasks/

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/327110
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=adf17f1e300eddfc2c41e0ebe40a11c2a3c76003
Submitter: Jenkins
Branch: master

commit adf17f1e300eddfc2c41e0ebe40a11c2a3c76003
Author: Vladimir Kuklin <email address hidden>
Date: Wed Jun 8 17:03:32 2016 +0300

    Fix master-node only graph processing

    Check for nodes list emptiness when discovering
    online nodes. With master-only graph we do not have
    any nodes except for virtual_sync_node and master.
    This leads to failure of mcollective discover
    as it receives an empty list

    Change-Id: I38bfd9b98f79ba83527de5956b66d2fc3ddb0020
    Closes-bug: #1590337

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/327151
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=390b257240d49cc5e94ed5c4fcd940b5f2f6ec64
Submitter: Jenkins
Branch: stable/mitaka

commit 390b257240d49cc5e94ed5c4fcd940b5f2f6ec64
Author: Vladimir Kuklin <email address hidden>
Date: Wed Jun 8 17:03:32 2016 +0300

    Fix master-node only graph processing

    Check for nodes list emptiness when discovering
    online nodes. With master-only graph we do not have
    any nodes except for virtual_sync_node and master.
    This leads to failure of mcollective discover
    as it receives an empty list

    Change-Id: I38bfd9b98f79ba83527de5956b66d2fc3ddb0020
    Closes-bug: #1590337

[Alexandr Kostrikov (akostrikov-mirantis)]

It has been fixed in swarm run: https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.custom_graph/20/testReport/(root)/master_node_tasks/master_node_tasks/