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

Bug #1653292 reported by Evgeniy L on 2016-12-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Evgeniy L
Evgeniy L

Bug Description

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.
 Update network verification graph
Description of the environment:
 master, stable/newton

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

Changed in fuel:
status: In Progress → Fix Committed

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

Changed in fuel:
milestone: 10.1 → 12.0

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/newton
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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers