Bug 1420280
| Summary: | "--api-version" option doesn't take effect for "oc config set-cluster" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yanping Zhang <yanpzhan> |
| Component: | oc | Assignee: | Fabiano Franz <ffranz> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.0 | CC: | aos-bugs, ffranz, hasha, jforrest, jokerman, mmccomas, smunilla, xiaocwan, xtian |
| Target Milestone: | --- | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:17:28 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
Yanping Zhang
2017-02-08 10:53:08 UTC
Related upstream PR: https://github.com/kubernetes/kubernetes/pull/41139 Upstream PR merged. Bug will be fixed in the next rebase. Fixed by the latest Kubernetes rebase. I checked the kubernetes PR 41139 is not rebased into latest Origin master yet (openshift v3.6.95 kubernetes v1.6.1+5115d708d7). So I changed to modified status, after the rebase is done please change back to ON_QA, Thanks! Pull request that deprecates --api-version is in https://github.com/openshift/origin/pull/14919. From PR https://github.com/openshift/origin/pull/14919, "--api-version" in oc config set-cluster is deprecated. Tested on oc v3.6.133 kubernetes v1.6.1+5115d708d7 It works as PR design now: # oc config view apiVersion: v1 clusters: - cluster: server: http://cow.org:8080 name: cow-cluster - cluster: insecure-skip-tls-verify: true server: https://xxx.com:8443 name: xxx-com:8443 <--snip--> This could be 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/RHEA-2017:1716 |