yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #61226
[Bug 1648095] Re: neutron-ns-metadata-proxy cleanup does not occur
Reviewed: https://review.openstack.org/428809
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=9a358fcfec20c5d69fac04f597776b52264c8b29
Submitter: Jenkins
Branch: master
commit 9a358fcfec20c5d69fac04f597776b52264c8b29
Author: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
Date: Fri Feb 3 08:38:06 2017 -0800
Revert "devstack: disable metadata for rally"
This reverts commit 9b371fe685032c9ab08fd1e99cf8583a6fbf11b5.
Change-Id: I56faa7d5cf9f5789da6a548f05bd37b2e8fc4da3
Closes-bug: #1648095
** Changed in: networking-odl
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/1648095
Title:
neutron-ns-metadata-proxy cleanup does not occur
Status in networking-odl:
Fix Released
Status in neutron:
Fix Released
Bug description:
Devstack + newton + networking-odl / v2.
To reproduce:
1. Create a new vxlan network.
2. Add 1 or more subnets
3. Delete the network.
I notice this occur during tempest.api.network.test_networks.NetworksIpV6Test.test_create_list_subnet_with_no_gw64_one_network
Finally linux is Out of memory and terminating processes based on
score.
Many like this;
stack 2538 1 0 11:19 ? 00:00:00 /usr/bin/python /usr/local/bin/neutron-ns-metadata-proxy --pid_file=/opt/stack/data/neutron/external/pids/b408d77c-ca69-4b2c-b2f1-5a889f149f11.pid --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy --network_id=b408d77c-ca69-4b2c-b2f1-5a889f149f11 --state_path=/opt/stack/data/neutron --metadata_port=80 --metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
stack 2981 1 0 11:20 ? 00:00:00 /usr/bin/python /usr/local/bin/neutron-ns-metadata-proxy --pid_file=/opt/stack/data/neutron/external/pids/ddfc2980-2c16-46f4-8eab-e91a047e796c.pid --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy --network_id=ddfc2980-2c16-46f4-8eab-e91a047e796c --state_path=/opt/stack/data/neutron --metadata_port=80 --metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
stack 4977 1 0 11:28 ? 00:00:00 /usr/bin/python /usr/local/bin/neutron-ns-metadata-proxy --pid_file=/opt/stack/data/neutron/external/pids/2b6d0fe6-f13a-4be4-9ea6-f6bc12ed3d69.pid --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy --network_id=2b6d0fe6-f13a-4be4-9ea6-f6bc12ed3d69 --state_path=/opt/stack/data/neutron --metadata_port=80 --metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
stack 6199 12085 0 11:34 pts/6 00:00:00 grep neutron-ns-metadata-proxy
stack 29462 1 0 11:11 ? 00:00:00 /usr/bin/python /usr/local/bin/neutron-ns-metadata-proxy --pid_file=/opt/stack/data/neutron/external/pids/00192768-29d1-46d2-9092-7a7bbd7b55ef.pid --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy --network_id=00192768-29d1-46d2-9092-7a7bbd7b55ef --state_path=/opt/stack/data/neutron --metadata_port=80 --metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
stack 32627 1 0 11:17 ? 00:00:00 /usr/bin/python /usr/local/bin/neutron-ns-metadata-proxy --pid_file=/opt/stack/data/neutron/external/pids/b2aa9b47-b55e-4b3f-bf2c-31bc91d86b33.pid --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy --network_id=b2aa9b47-b55e-4b3f-bf2c-31bc91d86b33 --state_path=/opt/stack/data/neutron --metadata_port=80 --metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1648095/+subscriptions