This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1471717 - oc version cannot get openshift version against ansible deployed service catalog env
oc version cannot get openshift version against ansible deployed service cata...
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: 3.7.0
Assigned To: Jeff Peeler
Xingxing Xia
Depends On:
  Show dependency treegraph
Reported: 2017-07-17 06:12 EDT by Xingxing Xia
Modified: 2017-10-18 21:51 EDT (History)
9 users (show)

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

Attachments (Terms of Use)

  None (edit)
Comment 1 Derek Carr 2017-07-17 10:55:30 EDT
target release for 3.7, as this should not block 3.6 release.

service catalog itself needs to report its own version.
Comment 2 Aleksandar Kostadinov 2017-08-07 05:30:31 EDT
"this should not block 3.6 release" but it actually breaks our test framework which relies on version checks to execute properly.

Is there any workaround to restore the endpoint, even if it is a hack to make env respond properly? This will help us fix the issue during env installation and then our code can execute as normal.
Comment 3 Xingxing Xia 2017-09-19 02:09:25 EDT
> oc version against env started by `oc cluster up ... --service-catalog` has same problem
FYI, checked with v3.7.0-0.126.4 env of `oc cluster up ... --service-catalog`, it can return openshift version (Ansible env still depends on bug 1486623)

$ oc version
oc v3.7.0-0.126.4
kubernetes v1.7.0+80709908fd
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://master:8443
openshift v3.7.0-0.126.4
kubernetes v1.7.0+80709908fd

Not return `service catalog itself ... own version` mentioned in comment 1, though.
Comment 4 Jay Boyd 2017-10-17 14:27:06 EDT
Still an open issue in upstream -

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