Description of problem: "svcat version" doesn't report version when it can't connect to server Version-Release number of selected component (if applicable): $ svcat version client: v0.1.13 server: v1.10.0+b81c8f8 How reproducible: Always Steps to Reproduce: 1. run "oc version" remotely . 2. run "svcat version" remotely when it can't connect to server. 3. run "svcat version" remotely when it can connect to server. Actual results: "svcat version" doesn't report version when it can't connect to server 1)[szh@localhost ~]$ oc version oc v3.9.11 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://host-8-250-216.host.centralci.eng.rdu2.redhat.com:8443 openshift v3.10.0-0.56.0 kubernetes v1.10.0+b81c8f8 2)[szh@localhost ~]$ svcat version Error: unable to get version, the server has asked for the client to provide credentials 3)[szh@localhost ~]$ oc login https://host-8-250-217.host.centralci.eng.rdu2.redhat.com:8443 [szh@localhost ~]$ svcat version client: v3.10.0-0.56.0;Upstream:v0.1.19 server: v1.10.0+b81c8f8 Expected results: "svcat version" report version when it can't connect to server Additional info:
svcat version --client looks to always work. Reviewing the code, this is working as intended. $ svcat version --help Provides the version for the Service Catalog client and server Usage: svcat version [flags] Examples: svcat version svcat version --client Flags: -c, --client Show only the client version I'm going to close this, looks to work as intended.
`oc` client works differently. If connection is impossible it shows only client version. If connection to server is possible it returns both versions. It is fine to have the `--client` option, but this doesn't mean we shouldn't offer a default behavior that makes more sense. I don't think existing code can be reason to close a bug about undesirable/confusing behavior. To me this behavior is inconsistent with existing cli tools and will likely be a source of confusion for users thus better be changed in line with existing cli tools we provide for OpenShift.
created upstream issue to rework svcat version reporting: https://github.com/kubernetes-incubator/service-catalog/issues/2092
fixed via upstream https://github.com/kubernetes-incubator/service-catalog/pull/2109 and included in OpenShift by https://github.com/openshift/service-catalog/releases/tag/v3.11.0-0.1.25 (builds newer then July 18)
Test with # svcat version Client Version: v3.11.0-0.16.0;Upstream:v0.1.27 Error: unable to get version, Get https://qe-dyan-311-master-etcd-1.0816-3r9.qe.rhcloud.com:8443/version?timeout=32s: dial tcp 104.198.144.246:8443: i/o timeout # oc plugin svcat version Client Version: v3.11.0-0.16.0;Upstream:v0.1.27 Error: unable to get version, Get https://qe-dyan-311-master-etcd-1.0816-3r9.qe.rhcloud.com:8443/version?timeout=32s: dial tcp 104.198.144.246:8443: i/o timeout error: exit status 1 could move to verified
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