Bug 1584696 - oc bash completion not up to date
Summary: oc bash completion not up to date
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.10.0
Assignee: Maciej Szulik
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 13:09 UTC by Mauricio Magnani
Modified: 2021-12-10 16:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 02:15:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0405 0 None None None 2019-03-14 02:15:41 UTC

Description Mauricio Magnani 2018-05-31 13:09:57 UTC
Description of problem:

oc bash completion is not completing everything.
Examples:
oc get deployment
oc get pvc
...

In origin however, these seem to be completed:
https://github.com/openshift/origin/blob/master/contrib/completions/bash/oc


Version-Release number of selected component (if applicable):

$ openshift version
openshift v3.9.27
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16


$ dzdo rpm -qa | grep openshift-ansible
openshift-ansible-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-roles-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-docs-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-playbooks-3.9.27-1.git.0.52e35b5.el7.noarch

Comment 1 Juan Vallejo 2018-05-31 13:58:19 UTC
Hi Mauricio, are you able to get any other commands to complete?
Have you made sure that the completion script has been sourced in your shell?

```
$ source <(oc completion bash)
```

Comment 2 Mauricio Magnani 2018-05-31 14:04:14 UTC
Hi Juan,

>>> are you able to get any other commands to complete?

yes, it's a very strange behavior. Some commands complete and others do not.

>>>Have you made sure that the completion script has been sourced in your shell?

yes, I checked again to make sure.

Comment 3 Juan Vallejo 2018-06-01 14:41:42 UTC
Hi Mauricio,

I have checked this with a newer client, and this issue no longer occurs as of v3.10. Moving this to ON_QA. Thanks

Comment 4 Xingxing Xia 2018-06-04 03:24:28 UTC
Verified in oc v3.10.0-0.54.0 which is yum installed/upgraded. The problem does not exist. What still exist are bug 1534371's some examples

Comment 7 errata-xmlrpc 2019-03-14 02:15:34 UTC
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-2019:0405


Note You need to log in before you can comment on or make changes to this bug.