Bug 1469448
Summary: | Need provide method to update broker status not only recreate | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | DeShuai Ma <dma> |
Component: | Service Broker | Assignee: | Paul Morie <pmorie> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.0 | CC: | aos-bugs, chezhang, jmatthew, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.7.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: | 2017-11-28 22:00:46 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
DeShuai Ma
2017-07-11 09:45:13 UTC
One thing to note is that the controller will re-list the broker according to an interval which is currently defined as a property of the service catalog controller. So, the controller will definitely eventually relist the broker. What we want to move to is: 1. An API field that sets the resync interval on a broker-specific basis 2. A porcelain command that allows the broker to be re-listed on demand The ansible broker team has volunteered to implement these things, and I have a meeting today to discuss it with them. Also, the broker should definitely be re-listed right away when the broker's spec is change. That part is a bug and will be fixed. Created https://github.com/kubernetes-incubator/service-catalog/issues/1018 to relist the broker immediately when the spec is changed. I don't consider this a blocker for 3.6 but I would like to ship the fix with 3.6 if possible. There are now two ways you can specify that a broker should be relisted: - A spec.relistBehavior field which can be "Manual" (relist the broker only when the user specifies) or "Duration" (relist on an internal, as specified by the spec.relistDuration field) - A spec.relistRequests field the user can bump to indicate that they want the broker to be relisted The fix LGTM except case2 in above description, it can be traced by another BZ https://bugzilla.redhat.com/show_bug.cgi?id=1499413 Verified in here. 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 |