Bug 1523335

Summary:	openshift_env facts overwrite top level keys
Product:	OpenShift Container Platform	Reporter:	Chad Scribner <cscribne>
Component:	Installer	Assignee:	Andrew Butcher <abutcher>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	aos-bugs, jokerman, mmccomas, mmckinst, sdodson
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	openshift-ansible-3.7.14-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-18 13:24:28 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 Chad Scribner 2017-12-07 18:14:22 UTC

openshift_env facts overwrite top level keys; a fix is present here: https://github.com/openshift/openshift-ansible/pull/6272

We need an rpm created that includes this fix as it's currently being patched manually.

Comment 1 Scott Dodson 2017-12-07 18:44:41 UTC

https://github.com/openshift/openshift-ansible/pull/6293 fix already backported

Comment 5 Gaoyun Pei 2017-12-11 10:06:41 UTC

The patch was merged into openshift-ansible-3.7.14-1.git.0.4b35b2d.el7.noarch. And no such error when trying ocp-3.7 installation with metrics enabled with external nfs.

With the following options added in ansible inventory file, start running playbooks/byo/config.yml
openshift_metrics_install_metrics=true
openshift_metrics_storage_kind=nfs
openshift_metrics_storage_host=10.x.x.x
openshift_metrics_storage_nfs_directory=/nfs/share/
openshift_metrics_storage_volume_name=metrics
openshift_metrics_image_prefix=registry.access.redhat.com/openshift3/
openshift_metrics_storage_labels={"storage": "metrics"}

Installation is successful and pv for metrics is created correctly.

Comment 8 errata-xmlrpc 2017-12-18 13:24:28 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-2017:3464