Network checker (custom graph) moves discovery node to error state

[Evgeniy L]

Steps to reproduce:
 Create cluster with nodes, wrongly configure networking, start network verification graph.
Expected results:
 Nodes are not moved to deployment error state.
Actual result:
 Nodes moved to error state which leads to provisioning/deployment logic which relies on nodes statuses.
Reproducibility:
 100%
Workaround:
 Update network verification graph
Description of the environment:
 master, stable/newton

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/415911
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b35486880eb0f15d4b522afff413880a8b9dd0a2
Submitter: Jenkins
Branch: master

commit b35486880eb0f15d4b522afff413880a8b9dd0a2
Author: Evgeny L <email address hidden>
Date: Wed Nov 30 01:44:12 2016 +0000

    After network checker is finished nodes must stay in discovery state

    Nodes should not be moved to error or ready states, when network
    checke process is finished.

    Closes-bug: #1653292
    Change-Id: I323efcea895f18206f8d8404aa3d870e3b1e7a51

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/429878

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/429878
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.