Bug 1690194
| Summary: | template-service-broker-operator is tsb-operator in origin, is not being built, and has no CI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
| Component: | Service Broker | Assignee: | Shawn Hurley <shurley> |
| Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, shurley |
| Target Milestone: | --- | Keywords: | BetaBlocker |
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:46:02 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
Clayton Coleman
2019-03-19 01:12:04 UTC
We have similar bug. FYI. https://bugzilla.redhat.com/show_bug.cgi?id=1685417 PR to fix names of ASB, ASBO, and TSBO: https://github.com/openshift/release/pull/3145 PRs to add CI are coming Marking this as done. The names have been updated and the CI tests are on their way. This should not block a release. Shawn, please share and correct me if I have a mistake. Thanks. Shawn, could you help to double confirm? Thanks. Hi, I don't believe this is correct https://github.com/openshift/release/tree/master/ci-operator/config/openshift/ansible-service-broker -> which does upstream stuff. https://github.com/openshift/release/tree/master/ci-operator/config/openshift/template-service-broker-operator I think it is probably important to note that these will not be apart of the released payload for openshift 4.0 as I understand it as they are optional installs. Shawn, thanks. 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-2019:0758 |