Red Hat Bugzilla – Bug 1540842
Failed to bind for jenkins-persistent(jenkins-ephemeral) serviceinstance
Last modified: 2018-03-28 10:25:20 EDT
Description of problem: Failed to bind for jenkins-persistent(jenkins-ephemeral) serviceinstance, met this error "ServiceBroker returned a failure; Bind operation will not be retried:Status: 500; ErrorMessage: <nil>; Description: no matches for /, Kind=Route;ResponseError: <nil>" Same scenario works for same version 'cluster up' env Version-Release number of selected component (if applicable): Server https://**** openshift v3.9.0-0.34.0 kubernetes v1.9.1+a0ce1bc657 How reproducible: always Steps to Reproduce: 1.Provision a jenkins-ephemeral serviceclass 2.Wait for serviceinstance ready, create a bind from webconsole 3.Check this servivebinding Actual results: oc get servicebinding jenkins-ephemeral-7dqmg-kldbf -n test -o yaml <--------------snip------------> name: jenkins-ephemeral-7dqmg-kldbf namespace: test resourceVersion: "42175" selfLink: /apis/servicecatalog.k8s.io/v1beta1/namespaces/test/servicebindings/jenkins-ephemeral-7dqmg-kldbf uid: 10845a67-0716-11e8-bdbb-0a580a020003 spec: externalID: 18384274-521f-4f7a-b136-9d3a7af02fc2 instanceRef: name: jenkins-ephemeral-7dqmg secretName: jenkins-ephemeral-7dqmg-credentials-87ult userInfo: extra: scopes.authorization.openshift.io: - user:full groups: - system:authenticated:oauth - system:authenticated uid: "" username: xiuwang status: conditions: - lastTransitionTime: 2018-02-01T06:06:38Z message: Orphan mitigation successful reason: OrphanMitigationSuccessful status: "False" type: Ready - lastTransitionTime: 2018-02-01T06:09:32Z message: 'ServiceBroker returned a failure; Bind operation will not be retried: Status: 500; ErrorMessage: <nil>; Description: no matches for /, Kind=Route; ResponseError: <nil>' reason: BindCallFailed status: "True" type: Failed orphanMitigationInProgress: false reconciledGeneration: 1 <-------------snip------------> Expected results: Should bind successfully Additional info:
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.
PR Created: https://github.com/openshift/openshift-ansible/pull/7251
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