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:
Bug Fixed with PR: https://github.com/openshift/ansible-service-broker/pull/474
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
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