Bug 1585127
Summary: | "svcat version" doesn't report version when it can't connect to server | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
Component: | Service Catalog | Assignee: | Jay Boyd <jaboyd> |
Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.10.0 | CC: | akostadi, chezhang, jaboyd, zhsun |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 3.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: If the cluster is not running or is not reachable, the command `svcat version` resulted in an error.
Fix: Code has been changed to always report the client version and if the server is reachable, it then reports the server version.
Result: The command `svcat version` now always reports the client version. If the server is available, it also reports the server version.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-11 07:20:33 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
sunzhaohua
2018-06-01 10:22:35 UTC
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 |