yahoo-eng-team team mailing list archive

[OpenStack Infra <1648095@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/411566
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a502c96b8efa62627e245ffa69a23f4b6d3f90a5
Submitter: Jenkins
Branch:    master

commit a502c96b8efa62627e245ffa69a23f4b6d3f90a5
Author: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
Date:   Thu Dec 15 17:05:26 2016 -0800

    Kill the metadata proxy process unconditionally
    
    When force_metadata=True and enable_isolated_metadata=False,
    the namespace metadata proxy process might not be terminated
    when the network is deleted because the subnets and ports
    will have already been deleted, so we could incorrectly
    determine it was started. Calling destroy_monitored_metadata_proxy() is
    a noop when there is no process running.
    
    Change-Id: I77ff545ce02f2dca4c38e587b37ea809ad6f072c
    Closes-Bug: #1648095


** 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/1648095

Title:
  neutron-ns-metadata-proxy cleanup does not occur

Status in networking-odl:
  In Progress
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