Network checker (custom graph) fails on scale

Bug #1653301 reported by Evgeniy L on 2016-12-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Sergii Golovatiuk
Newton
High
Sergii Golovatiuk

Bug Description

Detailed bug description:
 On 300 nodes environment network verification graph randomly fails on different nodes.
Description of the environment:
 stable/newton, master

Changed in fuel:
assignee: Evgeniy L (rustyrobot) → Sergii Golovatiuk (sgolovatiuk)

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

commit ebb761c872e46a7a6da902830a701fadda18846f
Author: Evgeny L <email address hidden>
Date: Wed Nov 23 22:48:28 2016 +0000

    Implement thread pool for network verification

    By default network checker runs ping to every ip
    in a thread simultaneously, depending on HW packets
    lost is possible, parallel_amount allows to configure
    how many pings should be run in parallel.

    Also add constraint on amount of connectivity checker
    tasks.

    Change-Id: I3aec37a2f50470cf905bccac34a6f79d2d5065d0
    Closes-bug: #1653301

Changed in fuel:
status: In Progress → Fix Committed

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

Changed in fuel:
milestone: 10.1 → 12.0

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