Red Hat Bugzilla – Bug 1504250
Ansible Service Broker stops listening for deprovision messages after failure
Last modified: 2018-07-18 22:56:50 EDT
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:
https://github.com/openshift/ansible-service-broker/pull/508
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
Remove the "NeedsTestCase" keywords since have already test case cover it.