neutron-ovs-cleanup failing when there are too many ports in bridge

Bug #1763604 reported by Slawek Kaplonski on 2018-04-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Medium
Ihar Hrachyshka

Bug Description

Patch https://review.openstack.org/#/c/536000/ improved a lot performance of neutron-ovs-cleanup utility but still if there is big number of ports in one bridge (e.g. 5000) neutron-ovs-cleanup utility might fails because of ovs connection timeout.

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

Changed in neutron:
status: Confirmed → In Progress
Changed in neutron:
assignee: Slawek Kaplonski (slaweq) → Brian Haley (brian-haley)
Changed in neutron:
assignee: Brian Haley (brian-haley) → Slawek Kaplonski (slaweq)
Changed in neutron:
assignee: Slawek Kaplonski (slaweq) → Ihar Hrachyshka (ihar-hrachyshka)

Reviewed: https://review.openstack.org/561186
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=806d96cbbe45fcd473935e777a2a56037fbb9d12
Submitter: Zuul
Branch: master

commit 806d96cbbe45fcd473935e777a2a56037fbb9d12
Author: Sławek Kapłoński <email address hidden>
Date: Fri Apr 13 11:34:42 2018 +0200

    Override ovsdb_timeout default value in ovs_cleanup tool

    In case when there is a lot of ports to clean in bridge, default
    ovsdb_timeout which is set for 10 seconds is not enough.
    This patch overrides default 10 seconds timeout in neutron-ovs-cleanup
    tool to 600 seconds.
    600 seconds value was tested experimentally on my dev environment for
    at least 10000 ports in bridge.

    In case when user will have more ports to delete with this script,
    it will be required to increase this ovsdb_timeout value in
    configuration.

    Change-Id: I79a554acdb1d6d61903be0c42d0215d302884e93
    Closes-Bug: #1763604

Changed in neutron:
status: In Progress → Fix Released

This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.

Reviewed: https://review.openstack.org/562147
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a82e9604f19121d6f72c098f826605c3326ebc54
Submitter: Zuul
Branch: stable/queens

commit a82e9604f19121d6f72c098f826605c3326ebc54
Author: Sławek Kapłoński <email address hidden>
Date: Fri Apr 13 11:34:42 2018 +0200

    Override ovsdb_timeout default value in ovs_cleanup tool

    In case when there is a lot of ports to clean in bridge, default
    ovsdb_timeout which is set for 10 seconds is not enough.
    This patch overrides default 10 seconds timeout in neutron-ovs-cleanup
    tool to 600 seconds.
    600 seconds value was tested experimentally on my dev environment for
    at least 10000 ports in bridge.

    In case when user will have more ports to delete with this script,
    it will be required to increase this ovsdb_timeout value in
    configuration.

    Change-Id: I79a554acdb1d6d61903be0c42d0215d302884e93
    Closes-Bug: #1763604
    (cherry picked from commit 806d96cbbe45fcd473935e777a2a56037fbb9d12)

tags: added: in-stable-queens

This issue was fixed in the openstack/neutron 12.0.2 release.

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

Other bug subscribers