Bug 1513497 – FQDN hieradata is hardcoded.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1513497 - FQDN hieradata is hardcoded.

Summary:	FQDN hieradata is hardcoded.

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-heat-templates (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	z3
Target Release:	12.0 (Pike)
Assigned To:	Emilien Macchi
QA Contact:	Pavan
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-15 09:23 EST by Juan Antonio Osorio
Modified:	2018-08-09 10:54 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	openstack-tripleo-heat-templates-7.0.12-1.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-07-25 10:19:24 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1732457	None	None	None	2017-11-15 09:23 EST
OpenStack gerrit	520082	None	None	None	2017-11-15 09:23 EST

Groups: None (edit)

Description Juan Antonio Osorio 2017-11-15 09:23:11 EST

Description of problem:

FQDN hieradata is hardcoded.

With the move to composable networks, most of the network-related bits are now dynamically generated with jinja. The only exception seems to be the FQDN hieradata keys, which still are hardcoded.

Which means that nay service that uses the FQDN hiera keys depending on the network will fail to do so on a custom network.

Version-Release number of selected component (if applicable):
OSP12

How reproducible:
100%

Steps to Reproduce:
1. Deploy the overcloud with a custom network (by modifying roles_data.yaml and network_data.yaml)
2. verify the fqdn_* hiera keys.

Actual results:
fqdn_* hiera keys are not generated for the custom network(s)

Expected results:
They should be generated.

Additional info:

Comment 3 Harry Rybacki 2018-01-30 11:28:25 EST

Moving this bug to post as upstream reviews have all merged and LP#1732457 shows fix-released. Will determine if change slipped into a zstream release at some point and update bug accordingly.

Comment 11 Juan Antonio Osorio 2018-07-25 10:19:24 EDT

This is already working in newer releases.

Note You need to log in before you can comment on or make changes to this bug.