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

Bug 1430661

Summary:	RFE: Add metricsPublicURL into master-config during ansible deployment for metrics
Product:	OpenShift Container Platform	Reporter:	Xia Zhao <xiazhao>
Component:	Installer	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Xia Zhao <xiazhao>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.5.0	CC:	aos-bugs, jkaur, jokerman, mmccomas, penli
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 21:53:01 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 Xia Zhao 2017-03-09 09:06:49 UTC

Description of problem:
Deploy logging with ansible, the loggingPublicURL will be automatically added into master-config, it'll be good metrics deployment can also add the metricsPublicURL there.

Version-Release number of selected component (if applicable):
openshift-ansible-3.5.28-1.git.0.103513e.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging and metrics with ansible
2.Check master-config

Actual results:
loggingPublicURL exists but metricsPublicURL didn't exist

Expected results:
it'll be good metrics deployment can also add the metricsPublicURL there

Additional info:

Comment 1 Jeff Cantrill 2017-03-10 20:20:09 UTC

https://github.com/openshift/openshift-ansible/pull/3625

Comment 2 openshift-github-bot 2017-03-11 15:04:32 UTC

Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/3c586308f6abe4451b022833291068900fe102fb
bug 1430661. Update masterConfig metricsPublicURL on install

Comment 8 errata-xmlrpc 2017-11-28 21:53:01 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/RHSA-2017:3188