We should disable or move to known issues test for disconnect controllers

[Tatyanka]

We should disable or move to known issues test for disconnect controllers

In tests we block input / output traffic on management net on 1 of controlelr at the same time we do not block nothing into namespaces, so that haproxy can balance request to failed controller (Because at this moment we support here only RR algorithm)
As result for most cases this tests may fail, to get it fixed we need to make feature request to make our haproxy possible to choose controller using some data (like load/ connectivity and etc)

So we propose to move this tests to known issue thread or disable it for some time

https://product-ci.infra.mirantis.net/job/7.0.system_test.ubuntu.ha_neutron_destructive/83/testReport/(root)/ha_neutron_disconnect_controllers/ha_neutron_disconnect_controllers/

[Vasily Gorin (vgorin)]

Maybe it is duplicate of https://bugs.launchpad.net/fuel/+bug/1493045

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/234376
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=f0fdd6c5102654892196c30e9873bb72ba2ce4fd
Submitter: Jenkins
Branch: master

commit f0fdd6c5102654892196c30e9873bb72ba2ce4fd
Author: Maksym Strukov <email address hidden>
Date: Tue Oct 13 21:08:07 2015 +0300

    Disable ha_neutron_disconnect_controllers system test

    In tests we block input / output traffic on management net on 1 of
    controlelr at the same time we do not block nothing into namespaces,
    so that haproxy can balance request to failed controller (Because at
    this moment we support here only RR algorithm). As result for most
    cases this tests may fail, to get it fixed we need to make feature
    request to make our haproxy possible to choose controller using some
    data (like load/ connectivity and etc)

    Change-Id: Ib019cdaf9c19145065d4ba5414e2509ce8854c4a
    Closes-Bug: #1493246