55874d06b1
It turns out that pyroute2.netns.setns() changes a network namespace of a thread instead of that of a process when it is called in a thread [1]. What we actually would like to check in test_in_namespace test is whether operations against a network namespace work with oslo.privsep expectedly. There is no need to check namespace inode. This commit changes test_in_namespace test to check a list of network devices in a namespace to check netns operation works correctly. What the new test does are: - create a network namespace for testing - create a veth pair and move one of them to the network namespace - call oslo.privsep entrypoint function to retrieve a list of network devices inside the netns [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001761.html Closes-Bug: #1811506 Change-Id: Ie5b238f1df707ea3ce50b5711ff791bac2681a2f |
||
|---|---|---|
| .. | ||
| contrib | ||
| etc/neutron/policy.d | ||
| fullstack | ||
| functional | ||
| tempest_plugin | ||
| unit | ||
| __init__.py | ||
| base.py | ||