Bug 1562337
Summary: | Servicebinding cannot be deleted when serviceinstance update to a invalid plan | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
Component: | Service Catalog | Assignee: | Paul Morie <pmorie> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, chezhang, jaboyd, jiazha, pmorie, zhsun, zitang |
Target Milestone: | --- | ||
Target Release: | 3.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | 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
Zhang Cheng
2018-03-30 08:56:55 UTC
Jay, would you take a look at this? I don't think you should be able to update to a plan that we know is invalid. We already have an admission controller runs against instance updates to make sure that the plan is updateable. We could extend that controller to ensure that the requested plan actually exists to avoid getting into the 'invalid plan' state to begin with. PR with the fix: https://github.com/kubernetes-incubator/service-catalog/pull/1922 We can't have the admission control plugin prevent users from pointing to a non-existent plan, because the plan may appear later. Fix has been merged. It will be included in v0.1.19 of Service Catalog upstream. Changing status to Modified since downstream image not ready for test. Changing status to ON_QA since downstream image ready for test. Verified and passed follow original test steps. # service-catalog --version v3.10.0-0.53.0;Upstream:v0.1.19 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 |