Bug 1480766 - kubectl 1.6.7 bash completion has invalid options
Summary: kubectl 1.6.7 bash completion has invalid options
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kubernetes
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Chaloupka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 20:29 UTC by Giovanni Tirloni
Modified: 2018-05-29 11:45 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:45:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Giovanni Tirloni 2017-08-11 20:29:24 UTC
Description of problem:
kubectl bash completion has invalid options

Version-Release number of selected component (if applicable):
kubernetes-client-1.6.7-1.fc26.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Type: kubectl get <tab>
2. See options available
3. Try `kubectl get status` or `kubectl get thirdpartyresourcedata` or `kubectl get cluster`

Actual results:
Error message is displayed: the server doesn't have a resource type "status"

Expected results:
These options are not available in completion options

Additional info:
Tested against minikube 1.7.3

Comment 1 Giovanni Tirloni 2017-08-11 20:33:36 UTC
Just noticed kubectl is at version 1.6.7. For some reason I thought Fedora already had 1.7.x. This is likely the issue here (version mismatch).

Comment 2 Giovanni Tirloni 2017-08-11 20:38:01 UTC
Maybe the bash completion does need an update. Tested against minikube 1.6.4 now but same results:

$ /usr/bin/kubectl version --short
Client Version: v1.6.7
Server Version: v1.6.4


$ /usr/bin/kubectl get 
certificatesigningrequest  event                      pod                        service
cluster                    horizontalpodautoscaler    poddisruptionbudget        serviceaccount
clusterrole                ingress                    podsecuritypolicy          statefulset
clusterrolebinding         job                        podtemplate                status
componentstatus            limitrange                 replicaset                 storageclass
configmap                  namespace                  replicationcontroller      thirdpartyresource
cronjob                    networkpolicy              resourcequota              thirdpartyresourcedata
daemonset                  node                       role                       
deployment                 persistentvolume           rolebinding                
endpoints                  persistentvolumeclaim      secret

Comment 3 Fedora End Of Life 2018-05-03 08:19:47 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2018-05-29 11:45:27 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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