Bug 1504250

Summary: Ansible Service Broker stops listening for deprovision messages after failure
Product: OpenShift Container Platform Reporter: David Zager <dzager>
Component: Service BrokerAssignee: David Zager <dzager>
Status: CLOSED ERRATA QA Contact: Jian Zhang <jiazha>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, jiazha, wmeng, xtian
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:18:08 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:
Attachments:
Description Flags
Ansible Service Broker's logs none

Description David Zager 2017-10-19 19:29:19 UTC 
Created attachment 1340904 [details]
Ansible Service Broker's logs

Description of problem:

When an APB fails deprovision, the broker stops listening for deprovisioning messages on it's channel. 

How reproducible: Always


Steps to Reproduce:
1. Start openshift origin with service catalog + ansible service broker (developer mode so that you can push APBs)
2. Push an APB that can fail on deprovision (https://github.com/djzager/fail-apb)
3. Provision the APB (if using fail-apb select the 'faildeprovision' plan)
4. Deprovision the APB
5. Provision another APB (ie. hello-world-apb)
6. Deprovision the APB

Actual results:

The deprovision complete message is put on the channel but the listener never receives it.

Expected results:

The listener to continue listening for deprovisioning messages on the channel.

Additional info:
Comment 1 David Zager 2017-10-19 22:22:43 UTC 
https://github.com/openshift/ansible-service-broker/pull/508
Comment 6 errata-xmlrpc 2017-11-28 22:18:08 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
Comment 7 Jian Zhang 2018-07-19 02:56:50 UTC 
Remove the "NeedsTestCase" keywords since have already test case cover it.