Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685189 - oc get clusteroperators -o wide -w ignores the wide output option when used in a watch
Summary: oc get clusteroperators -o wide -w ignores the wide output option when used i...
Keywords:
Status: ASSIGNED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Mike Dame
QA Contact: Xingxing Xia
URL:
Whiteboard:
: 1690263 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 15:06 UTC by Mike Fiedler
Modified: 2019-04-09 11:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Mike Fiedler 2019-03-04 15:06:58 UTC
Description of problem:

oc clusteroperators -o wide works fine - it shows the clusteroperator status.

However, if you set a watch, the wide is ignored:

# oc get clusteroperators -o wide -w
NAME                                  AGE
cluster-autoscaler                    28m
cluster-storage-operator              26m
console                               26m
dns                                   41m
image-registry                        26m
ingress                               26m
kube-apiserver                        38m
kube-controller-manager               34m
kube-scheduler                        36m
machine-api                           29m
machine-config                        29m
marketplace-operator                  26m
monitoring                            26m
network                               42m
node-tuning                           26m
openshift-apiserver                   28m
openshift-authentication              30m
openshift-cloud-credential-operator   29m
openshift-controller-manager          27m
openshift-samples                     26m
operator-lifecycle-manager            28m



Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-03-04-114357



How reproducible: Always

Comment 1 Mike Dame 2019-04-02 18:32:47 UTC
Upping log levels I see instances of:

I0402 14:29:59.469792   32068 get.go:707] Unable to convert *unstructured.Unstructured to config.openshift.io/__internal: no kind "ClusterOperator" is registered for version "config.openshift.io/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:29"

when replicating this problem, which leads to a problem converting to internal version here: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/get/get.go#L703. looking further into this

Comment 2 Mike Dame 2019-04-02 18:33:36 UTC
Also note that this looks similar/duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1690263

Comment 3 Mike Fiedler 2019-04-02 18:50:38 UTC
clusterversion has the issue too.

Comment 4 Mike Dame 2019-04-04 15:15:30 UTC
Also reported in upstream: https://github.com/kubernetes/kubernetes/issues/66538

Comment 5 Mike Dame 2019-04-05 19:53:52 UTC
*** Bug 1690263 has been marked as a duplicate of this bug. ***

Comment 6 Mike Dame 2019-04-08 16:04:20 UTC
A fix for this has been merged into upstream 1.15 https://github.com/kubernetes/kubernetes/pull/76161

Comment 7 Maciej Szulik 2019-04-09 11:13:35 UTC
Discussed this during blocker bug call and with Clayton, we'll try to back port this when we bump to k8s 1.14, not sooner. Thus I'm moving target to 4.2 for now.


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