Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1439855

Summary:	[OSP11] neutron-ns-metadata-proxy has a large memory footprint
Product:	Red Hat OpenStack	Reporter:	Daniel Alvarez Sanchez <dalvarez>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED ERRATA	QA Contact:	Roee Agiman <ragiman>
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	amuller, chrisw, dnavale, jlibosva, nyechiel, oblaut, samccann, srevivo, tfreger
Target Milestone:	z2	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-10.0.2-3.el7ost	Doc Type:	Enhancement
Doc Text:	A high memory consumption was observed, especially in large environments, which often led to out-of-memory issues. The main culprit was neutron-ns-metadata-proxy process, responsible for proxying metadata requests from the VM to Nova. neutron-ns-metadata-proxy is now replaced by haproxy which has a more lightweight memory footprint.	Story Points:	---
Clone Of:	1438469	Environment:
Last Closed:	2017-09-13 21:47:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1438469
Bug Blocks:

Description Daniel Alvarez Sanchez 2017-04-06 17:10:17 UTC

+++ This bug was initially created as a clone of Bug #1438469 +++

Currently, neutron-ns-metadata-proxy process has a large memory footprint [0] and, in large environments this could lead to OOM killers.

Some weeks ago, we got a patch merged upstream that switched metadata proxy Python implementation to haproxy. This reduced memory consumption dramatically and backporting it to OSP10 would really help.


[0] https://snapshot.raintank.io/dashboard/snapshot/AJoRIgEOpgpPpD9GYxeT1ZkAzbIwisn1

Comment 1 Jakub Libosvar 2017-04-07 08:13:37 UTC

*** Bug 1439856 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2017-09-13 21:47:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2714