Bug 1562732
Summary: | Deleting serviceinstance fail occasionally | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zihan Tang <zitang> |
Component: | Service Broker | Assignee: | Jesus M. Rodriguez <jesusr> |
Status: | CLOSED ERRATA | QA Contact: | Zihan Tang <zitang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, chezhang, pmorie |
Target Milestone: | --- | ||
Target Release: | 3.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Invalid deprovision response combined with an error during deprovision caused deprovisions to fail occasionally.
Consequence:
Deprovisions would fail.
Fix:
Return the proper deprovision response body with the operation key, as well as a variety of changes to the deprovision workflow to address other bugs fixed the failed jobs.
Result:
Deprovisions will have a higher likelihood of succeeding now.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-30 19:11:39 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: |
Description
Zihan Tang
2018-04-02 09:41:25 UTC
Please retest this with a new Automation Broker 1.2.8, as a lot has changed in this area of code to fix a variety of issues including some of the deprovision issues. Thanks Jesus, We will run regression test in recent run , If it can not reproduced , we'll mark it as verified. Before re-testing, we should wait for this fix to arrive in a build. I think it is related. https://github.com/openshift/ansible-service-broker/pull/942 Available in asb 1.2.11 In recent runs against 3.10, we haven't reproduce it. So mark it as Verified. If we reproduce in 3.10 once again, I'll reopen it. 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:1816 |