Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1609676 - Fail to bind jenkins-persistent(jenkins-ephemeral) serviceinstance
Fail to bind jenkins-persistent(jenkins-ephemeral) serviceinstance
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.11.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Erik Nelson
Wenjing Zheng
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-30 03:30 EDT by Wenjing Zheng
Modified: 2018-10-11 03:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:22:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:22 EDT

  None (edit)
Description Wenjing Zheng 2018-07-30 03:30:57 EDT
Description of problem:
Failed to bind for jenkins-persistent(jenkins-ephemeral) serviceinstance, met this error 'ServiceBroker returned failure; bind operation will not be retried:
        Status: 500; ErrorMessage: <nil>; Description: FindResults failed on annotation
        template.openshift.io/expose-uri: path is not found; ResponseError: <nil>'


Version-Release number of selected component (if applicable):
v3.11.0-0.10.0

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 
  status:
    asyncOpInProgress: false
    conditions:
    - lastTransitionTime: 2018-07-30T06:57:11Z
      message: Orphan mitigation was completed successfully
      reason: OrphanMitigationSuccessful
      status: "False"
      type: Ready
    - lastTransitionTime: 2018-07-30T06:59:56Z
      message: 'ServiceBroker returned failure; bind operation will not be retried:
        Status: 500; ErrorMessage: <nil>; Description: FindResults failed on annotation
        template.openshift.io/expose-uri: path is not found; ResponseError: <nil>'
      reason: ServiceBindingReturnedFailure
      status: "True"
      type: Failed
    orphanMitigationInProgress: false
    reconciledGeneration: 1
    unbindStatus: Succeeded


Expected results:
Should bind successfully

Additional info:
Comment 2 Erik Nelson 2018-08-16 10:03:43 EDT
On second thought, we're going to close the above PR and instead update the broker code to silently ignore a failed json path lookup to maintain consistent behavior with 3.10.
Comment 3 Erik Nelson 2018-08-28 09:38:03 EDT
The following fix should preserve existing behavior while also allowing for missing path lookups: https://github.com/openshift/origin/pull/20774
Comment 4 openshift-github-bot 2018-08-28 10:57:31 EDT
Commits pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/2b48b4ec7492e7881dd8c8e510ba5ecb80aa70d2
Bug 1609676 - Fix missing bind values regression

https://github.com/openshift/origin/commit/ae86f050353088f6ce750fd0d3d418ba58b42563
Merge pull request #20774 from eriknelson/bz1609676

Bug 1609676 - Fix missing bind values regression
Comment 6 Wenjing Zheng 2018-09-06 04:22:32 EDT
No such error when provision jenkins template on openshift v3.11.0-0.28.0:
  status:
    asyncOpInProgress: false
    conditions:
    - lastTransitionTime: 2018-09-06T08:10:41Z
      message: Injected bind result
      reason: InjectedBindResult
      status: "True"
      type: Ready
Comment 8 errata-xmlrpc 2018-10-11 03:22:24 EDT
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:2652

Note You need to log in before you can comment on or make changes to this bug.