Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1543044 - [3.7] Failed to unbind after deleting templateinstance with servicebinding existing
[3.7] Failed to unbind after deleting templateinstance with servicebinding ex...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.1
Unspecified Unspecified
medium Severity low
: ---
: 3.7.z
Assigned To: Ben Parees
Wenjing Zheng
: Reopened
Depends On: 1540819
Blocks: 1543039
  Show dependency treegraph
 
Reported: 2018-02-07 10:46 EST by Ben Parees
Modified: 2018-06-07 08:40 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Unbinding a template service instance throws an error if the template service instance was deleted. Consequence: It becomes impossible to unbind a service instance if the template service instance was manually deleted, including if the project containing the TSI was deleted. Fix: The template service broker will return success/gone in cases where the unbind refers to a non-existent template service instance. Result: The unbind can proceed even if the TSI no longer exists.
Story Points: ---
Clone Of: 1540819
Environment:
Last Closed: 2018-06-07 08:40:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:39 EDT

  None (edit)
Comment 3 XiuJuan Wang 2018-02-13 01:23:59 EST
Could unbind after deleting templateinstance with servicebinding existing.
Can't reproduce this bug in ocp v3.7.29 with service-catalog(image id ce5cecc95a66) and ose(image id 67270b3564b7) images
Comment 7 errata-xmlrpc 2018-04-05 05:38:31 EDT
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/RHBA-2018:0636

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