Bug 1511186

Summary:	Keep Namespace On Error Configuration Value Should be Set For openshift ansible
Product:	OpenShift Container Platform	Reporter:	Shawn Hurley <shurley>
Component:	Installer	Assignee:	Shawn Hurley <shurley>
Status:	CLOSED ERRATA	QA Contact:	Zhang Cheng <chezhang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, chezhang, jmatthew, jokerman, mmccomas, wmeng
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 22:22:19 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 Shawn Hurley 2017-11-08 20:42:21 UTC

Description of problem:
During ASB install for Openshift ansible we would expect that the keep_namespace_on_error value in the broker configuration file to be set to true.

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


How reproducible:
Always 

Steps to Reproduce:
1. Run openshift installer
2.
3.

Actual results:
keep_namespace_on_error is not set.

Expected results:
keep_namespace_on_error should be set to true in the broker config

Additional info:

Comment 1 Shawn Hurley 2017-11-08 20:59:34 UTC

Fixed in PR: https://github.com/openshift/openshift-ansible/pull/6067

Comment 3 Zhang Cheng 2017-11-09 08:14:20 UTC

Verified with openshift-ansible-3.7.4-1
keep_namespace_on_error: true (by default)

Comment 4 John Matthews 2017-11-09 19:34:09 UTC

*** Bug 1510406 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2017-11-28 22:22:19 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