yahoo-eng-team team mailing list archive

[OpenStack Infra <1763604@xxxxxxxxxxxxxxxxxx>]

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 <slawek@xxxxxxxxxxxx>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763604

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

Status in neutron:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1763604/+subscriptions