Don't use duplicate filter names for functional testing

They are not supported by Python 3.x configparser module (you get
DuplicateOptionError if duplicate names are present).

This makes tests relying on rootwrap daemon to get stuck, because the daemon
fails to spawn, while we wait for results from the process.

Change-Id: I1628bb87b235a6b4bac53afda37402e986520f39
Related-Bug: #1515118

diff --git a/neutron/tests/contrib/functional-testing.filters b/neutron/tests/contrib/functional-testing.filters
index 17d635d06582a6a53742ef3fa0e9133d95cf8555..40a45047953547249282c317506e3040f21d2fed 100644 (file)
--- a/neutron/tests/contrib/functional-testing.filters
+++ b/neutron/tests/contrib/functional-testing.filters
@@ -32,4 +32,4 @@ dhclient_kill: KillFilter, root, dhclient, -9
 mkdir_filter: RegExpFilter, /bin/mkdir, root, mkdir, -p, /etc/netns/qdhcp-[0-9a-z./-]+
 rm_filter: RegExpFilter, /bin/rm, root, rm, -r, /etc/netns/qdhcp-[0-9a-z./-]+
 touch_filter: RegExpFilter, /bin/touch, root, touch, /etc/netns/qdhcp-[0-9a-z./-]+/resolv.conf
-touch_filter: RegExpFilter, /usr/bin/touch, root, touch, /etc/netns/qdhcp-[0-9a-z./-]+/resolv.conf
+touch_filter2: RegExpFilter, /usr/bin/touch, root, touch, /etc/netns/qdhcp-[0-9a-z./-]+/resolv.conf