Bug 1504250 - Ansible Service Broker stops listening for deprovision messages after failure
Summary: Ansible Service Broker stops listening for deprovision messages after failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.7.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 3.7.0
Assignee: David Zager
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-19 19:29 UTC by David Zager
Modified: 2018-07-19 02:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:18:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Ansible Service Broker's logs (84.68 KB, text/plain)
2017-10-19 19:29 UTC, David Zager
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

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 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.


Note You need to log in before you can comment on or make changes to this bug.