Description of problem: Version-Release number of selected component (if applicable): ~ oc version --client Client Version: v4.2.11 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: https://coreos.slack.com/archives/CEKNRGF25/p1578065888081000 David Eads 39 minutes ago --kubeconfig should work. If it does not work, that is a bug David Eads 40 minutes ago --config is required for backward compatibility. @maszulik I think you can deprecate and hide it now, but leave it in place Additional info: ➜ ~ mv ~/.kube/config /tmp/tmp.config ➜ ~ oc --kubeconfig /tmp/tmp.config config view apiVersion: v1 clusters: [] contexts: [] current-context: "" kind: Config preferences: {} users: [] ### --config works ➜ ~ oc --config /tmp/tmp.config config view apiVersion: v1 clusters: - cluster: server: https://api.ci.openshift.org:443 name: api-ci-openshift-org:443 contexts: - context: cluster: api-ci-openshift-org:443 namespace: default user: hongkailiu/api-ci-openshift-org:443 name: default/api-ci-openshift-org:443/hongkailiu ...
Confirmed with latest oc client, the issue has fixed: [zhouying@dhcp-140-138 test-bugs]$ rpm -q openshift-clients openshift-clients-4.4.0-202001091623.git.1.670f92e.el7.x86_64 [zhouying@dhcp-140-138 test-bugs]$ oc config view apiVersion: v1 clusters: null contexts: null current-context: "" kind: Config preferences: {} users: null [zhouying@dhcp-140-138 test-bugs]$ oc --kubeconfig /tmp/config.tmp config view apiVersion: v1 clusters: - cluster: server: https://xxxxx:443 name: xxxxxx:443 - cluster: insecure-skip-tls-verify: true server: https://yyyyy:6443 name: yyyyy:6443 ....
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-2020:0581