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

Bug 1617094

Summary:	A deprecated parameter, nova_metadata_ip is configured in RHOSP13
Product:	Red Hat OpenStack	Reporter:	Keigo Noha <knoha>
Component:	openstack-tripleo-heat-templates	Assignee:	Kamil Sambor <ksambor>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	beagles, jjoyce, jschluet, knoha, ksambor, mburns, sclewis, slinaber, tvignaud
Target Milestone:	z7	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.3.1-23.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1708169 1708170 (view as bug list)		Environment:
Last Closed:	2019-07-10 13:03:16 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:	1708169, 1708170

Description Keigo Noha 2018-08-16 02:43:26 UTC

Description of problem:
A deprecated parameter, nova_metadata_ip is configured in RHOSP13

Version-Release number of selected component (if applicable):
Current puppet-neutron

How reproducible:
Every time

Steps to Reproduce:
1. Deploy overcloud.
2.
3.

Actual results:
nova_metadata_ip is configured.

Expected results:
nova_metadata_host is configured.

Additional info:
The deprecation is done in https://github.com/openstack/neutron/commit/366dd7cc37c053e0fff897b16414c960243abcfc#diff-d1f56fc8244c8f48b8c399a63fd93077

Comment 1 Brent Eagles 2018-08-17 12:47:24 UTC

Is nova_metadata_host *not* being configured in their deployment? That is unexpected as support for configuring that should have been added in this patch https://review.openstack.org/#/c/494658/

Comment 2 Keigo Noha 2018-08-27 01:59:48 UTC

Hello Brent,

They use nova_metadata_host parameter. But nova_metada_ip is also configured.

In my testing environment deployed with infrared, /var/lib/config-data/puppet-generated/neutron/etc/neutron/metadata_agent.ini has nova_metada_host and nova_metada_ip in it.

Their request is nova_metadata_ip should not be configured with puppet-neutron because it is deprecated.

How do you think about it?

Best Regards,
Keigo Noha

Comment 3 Brent Eagles 2018-08-27 13:16:59 UTC

I agree. I just wanted to make sure the correct parameter was being set. We are in the process of submitting the patches for removing this parameter from puppet, etc. upstream. Thanks for pointing this out!

Comment 4 Kamil Sambor 2018-09-24 09:17:06 UTC

Changes was merged and will be relesed in Stein branch. IMHO there is no reason for backporting changes because argument nova_metadata_host which replace deprecated nova_metadata_ip can be set in osp13 and nova_metadata_ip not effect anything. Merged patch was simply cleaning of codebase.

Comment 10 Keigo Noha 2019-05-09 09:20:28 UTC

Hi Kamil,

Could you consider to proceed this bugzilla forward?

Best Regards,
Keigo Noha

Comment 26 errata-xmlrpc 2019-07-10 13:03:16 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-2019:1738