| Summary: | Usage of some oc commands may be misleading due to 'options' is put after 'COMMAND' such as oc set probe, oc debug etc | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Peter Ruan <pruan> |
| Component: | oc | Assignee: | Fabiano Franz <ffranz> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Xingxing Xia <xxia> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.x | CC: | aos-bugs, dyan, mmccomas, xxia |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-19 13:51:30 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: | |
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. *** Thanks. VERIFIED in oc v1.3.0-alpha.2-381-gd81b0cc. Now 'options' is put before 'COMMAND' in sub-command usage help info |
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: