Bug 1540842
Summary: | Failed to bind for jenkins-persistent(jenkins-ephemeral) serviceinstance | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
Component: | Installer | Assignee: | Michael Gugino <mgugino> |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, chezhang, jmatthew, jokerman, mmccomas, wzheng |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | 3.9.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-03-28 14:24:57 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
XiuJuan Wang
2018-02-01 06:32:39 UTC
I haven't been able to recreate this on origin latest. Do you have an environment I can see? Part of the problem is that the TSB version is v3.7 and the cluster version is v3.9. This should be resolved by https://github.com/openshift/openshift-ansible/pull/6712. It's not yet clear what is causing running TSB v3.7 on cluster v3.9 to be problematic. Actually, running TSB v3.7 on cluster v3.9 works, I made a configuration error when I was testing it. (In reply to Jim Minter from comment #4) > Actually, running TSB v3.7 on cluster v3.9 works, I made a configuration > error when I was testing it. Good, ensuring this works is critical to performing upgrades as TSB and other components running atop the cluster will upgrade from 3.7 to 3.9 after the API/Controllers have already been upgraded from 3.7 to 3.8 to 3.9. Could bind for jenkins-persistent(jenkins-ephemeral) serviceinstance. Verified with ose-template-service-broker:v3.9.2 openshift v3.9.2 kubernetes v1.9.1+a0ce1bc657 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:0489 |