Bug 1497766

Summary:	APB Pods are deleted even when an error occurs
Product:	OpenShift Container Platform	Reporter:	Shawn Hurley <shurley>
Component:	Service Broker	Assignee:	Shawn Hurley <shurley>
Status:	CLOSED ERRATA	QA Contact:	Qixuan Wang <qixuan.wang>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.7.0	CC:	aos-bugs, chezhang, jmatthew, 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:14:33 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-10-02 15:40:44 UTC

Description of problem:
When the ASB executes the APB pod it will delete the pod even when there is an error. This makes it very hard to debug APB issues

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


How reproducible:
Always


Steps to Reproduce:
1. Run a provision on a bad APB
2.
3.

Actual results:
APB is deleted 

Expected results:
APB should not be deleted if an error occurs and that behavior has been defined.

Additional info:

Comment 1 Shawn Hurley 2017-10-13 16:59:03 UTC

Bug Fixed with PR: https://github.com/openshift/ansible-service-broker/pull/474

Comment 3 Qixuan Wang 2017-10-20 10:00:47 UTC

Tested on OCP (openshift v3.7.0-0.158.0, kubernetes v1.7.6+a08f5eeb62, etcd 3.2.8）. The bug has been fixed, thanks.

Established service-catalog and ansible-service-broker.
On web console, provision an Etherpad(APB), there is an error in etherpad pod, and it won't be deleted.
 
(apb) [root@preserve-qw-master-etcd-1 ~]# oc get pod -n qwang1
NAME               READY     STATUS             RESTARTS   AGE
etherpad-1-mbv1g   0/1       CrashLoopBackOff   6          10m
mariadb-1-9pjg1    1/1       Running            0          10m

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