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

Bug 1438469

Summary:	[OSP10] neutron-ns-metadata-proxy has a large memory footprint
Product:	Red Hat OpenStack	Reporter:	Daniel Alvarez Sanchez <dalvarez>
Component:	openstack-neutron	Assignee:	Daniel Alvarez Sanchez <dalvarez>
Status:	CLOSED ERRATA	QA Contact:	GenadiC <gcheresh>
Severity:	high	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	amuller, chrisw, jlibosva, nyechiel, oblaut, samccann, srevivo
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-9.3.1-8.el7ost	Doc Type:	Enhancement
Doc Text:	The neutron-ns-metadata-proxy process can cause high memory consumption, especially in large environments. This can lead to Out-Of-Memory issues. The neutron-ns-metadata-proxy is now replaced by haproxy which has a more lightweight memory footprint. The haproxy now proxies meta data requests from the guest VM to the Compute node (nova).	Story Points:	---
Clone Of:
Clones:	1439855 1439856 (view as bug list)		Environment:
Last Closed:	2017-09-06 17:17:18 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:
Bug Blocks:	1439855, 1439856

Description Daniel Alvarez Sanchez 2017-04-03 13:18:54 UTC

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 6 GenadiC 2017-08-17 14:08:19 UTC

Verified on openstack-neutron-9.4.0-2.el7ost.noarch.
1) Code verification
2) Created a router and made sure that running ps -ef | grep haproxy returned /var/lib/neutron/ns-metadata-proxy/<router_id>.conf
3) No neutron-ns-metadata-proxy process running

Comment 8 errata-xmlrpc 2017-09-06 17:17:18 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:2663