Hide Forgot
Description of problem: The double dash used by 'oc debug' get confused with user also specify a config location. Version-Release number of selected component (if applicable): oc v3.2.0.4 kubernetes v1.2.0-origin-41-g91d3e75 How reproducible: always. Steps to Reproduce: 1. oc debug -f pod_simple.yaml -- /bin/env --config=/home/pruan/workdir/dhcp-16-139-pruan/ose_pruan1.kubeconfig 2. 3. Actual results: oc debug -f pod_simple.yaml -- /bin/env --config=/home/pruan/workdir/dhcp-16-139-pruan/ose_pruan1.kubeconfig error: unable to connect to a server to handle "pods": No configuration file found, please login or point to an existing file: 1. Via the command-line flag --config 2. Via the KUBECONFIG environment variable 3. In your home directory as ~/.kube/config To view or setup config directly use the 'config' command. Expected results: Additional info:
Better to update usage info, like `oc exec -h` which differentiate between and order oc options and COMMAND args
*** Bug 1330845 has been marked as a duplicate of this bug. ***
Fixed in https://github.com/openshift/origin/pull/9693
Thanks. VERIFIED in oc v1.3.0-alpha.2-381-gd81b0cc. Now 'options' is put before 'COMMAND' in sub-command usage help info