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

Bug 1565288

Summary:	Customize Container Service Port Needs to Update Health Checks and Container
Product:	Red Hat OpenStack	Reporter:	Benjamin Schmaus <bschmaus>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Magr <mmagr>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12.0 (Pike)	CC:	bdobreli, mburns, ohochman, pkilambi, rhel-osp-director-maint, sbaker
Target Milestone:	z5	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.0.7-34.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-14 13:54:50 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:

Description Benjamin Schmaus 2018-04-09 19:16:03 UTC

Description of problem:

In Director we can define a custom port for a overcloud service to run on, for example Redis.    However this defined port is not configured in the container or the health check.


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

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Default port is used in container image and health check

Expected results:
Custom port defined in template should be applied via Ansible to running container environment and health check should be configured to check proper port

Additional info:

Comment 2 Steve Baker 2018-05-14 20:16:38 UTC

Assigning this healthcheck issue to DF:MetMon

Comment 23 errata-xmlrpc 2019-03-14 13:54:50 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:0448