Bug 1579866

Summary:	Metadata API is still using eventlet which will be deprecated in OSP14
Product:	Red Hat OpenStack	Reporter:	Sylvain Bauza <sbauza>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	berrange, dasmith, dbecker, eglynn, jamsmith, jhakimra, kchamart, lyarwood, mburns, morazi, mschuppe, owalsh, sbauza, sgordon, srevivo, vromanso
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.0.0-0.20180919080944.0rc1.0rc1.el7ost puppet-nova-13.3.1-0.20180917153245.6fdb591.el7ost	Doc Type:	Bug Fix
Doc Text:	With this change nova-metadata-api is served via httpd wsgi in the nova_metadata container. Note that upstream will deprecate usage of eventlet for all the WSGI-run services, including nova-api and nova-metadata-api. See https://review.openstack.org/#/c/549510/ for more details.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:49:53 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:	1637739
Bug Blocks:

Description Sylvain Bauza 2018-05-18 14:11:45 UTC

Upstream will deprecate usage of eventlet of all the WSGI-run services, including nova-api and nova-metadata-api.
See https://review.openstack.org/#/c/549510/ for more details.

OSP13 runs nova-api through HTTPd already [1], so we're clear for the the former, but the latter (nova-metadata-api) requires a bit of work [2].

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/nova-api.yaml#L112

[2] https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/nova-metadata.yaml#L85

To make it clear, given upstream change, our customers would see a warning in the metadata service logs if we don't fix that for OSP14, which I guess is a bad experience for them as it could confuse them.

Comment 10 errata-xmlrpc 2019-01-11 11:49:53 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/RHEA-2019:0045