Reviewed: https://review.opendev.org/c/openstack/neutron/+/814868 Committed: https://opendev.org/openstack/neutron/commit/8127221479834350465251839ab88056f4f64fb4 Submitter: "Zuul (22348)" Branch: master
commit 8127221479834350465251839ab88056f4f64fb4 Author: Rodolfo Alonso Hernandez <[email protected]> Date: Thu Oct 21 08:49:41 2021 +0000 Check a namespace existence by checking only its own directory To check the existance of a namespace, instead of listing the namespaces directory (by default "/var/run/netns"), this patch directly checks the existence of the namespace directory, using "os.path.exists". This check is faster than listing the whole directory and avoids timeout problems as reported in the related bug. Closes-Bug: #1947974 Change-Id: I558d50d28378beb3710d98a2113ff9549c82ae17 ** 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/1947974 Title: "network_namespace_exists"can timeout in loaded systems Status in neutron: Fix Released Bug description: The method "neutron.agent.linux.ip_lib.network_namespace_exists" can timeout in loaded systems. We have detected this problem during some capacity tests. During those tests, the controllers are creating and deleting networks; that implies the creation and deletion of DHCP namespaces "qdhcp-xxx" in the same hosts. Adding additional logs (tagged with "SK;"), we found this method was timing out. Snippet: https://paste.opendev.org/show/810132/ New additional logs added: https://paste.opendev.org/show/810133/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1947974/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
