Description of problem: When calling 'oc get clusterrolebinding.rbac' command with '-o wide' option it reports columns of 'ROLE', 'USERS', 'GROUPS', 'SERVICEACCOUNTS' were added until OCP4.2, but they have not been added after OCP4.3. I think they should be added. It might be the effect of the following changes but '--server-print=false' option does not work. https://github.com/kubernetes/enhancements/issues/515 Version-Release number of selected component (if applicable): 4.4 4.3 How reproducible: Always Steps to Reproduce: 1. Call 'oc get clusterrolebinding.rbac -o wide' via admin Actual results: # OCP4.3 $ oc version Client Version: 4.3.3 Server Version: 4.3.3 Kubernetes Version: v1.16.2 $ oc get clusterrolebinding.rbac -o wide --server-print=false | head # using `--server-print` option with false NAME AGE alertmanager-main 2d18h basic-users 2d18h cloud-credential-operator-rolebinding 2d18h cluster-admin 2d18h cluster-admin-0 25h cluster-admins 2d18h cluster-autoscaler 2d18h cluster-autoscaler-operator 2d18h cluster-logging-metadata-reader 25h $ oc get clusterrolebinding.rbac -o wide --server-print=true | head NAME AGE alertmanager-main 2d19h basic-users 2d19h cloud-credential-operator-rolebinding 2d19h cluster-admin 2d19h cluster-admin-0 25h cluster-admins 2d19h cluster-autoscaler 2d19h cluster-autoscaler-operator 2d19h cluster-logging-metadata-reader 26h # OCP4.4 $ oc version Client Version: 4.4.0-0.nightly-2020-02-02-225006 Server Version: 4.4.0-0.nightly-2019-11-26-041012 Kubernetes Version: v1.16.2 $ oc get clusterrolebinding.rbac -o wide --server-print=false | head # using `--server-print` option with false NAME AGE alertmanager-main 29d basic-users 29d cloud-credential-operator-rolebinding 29d cluster-admin 29d cluster-admin-0 12d cluster-admins 29d cluster-autoscaler 29d cluster-autoscaler-operator 29d cluster-logging-metadata-reader 8d $ oc get clusterrolebinding.rbac -o wide --server-print=true | head NAME AGE alertmanager-main 29d basic-users 29d cloud-credential-operator-rolebinding 29d cluster-admin 29d cluster-admin-0 12d cluster-admins 29d cluster-autoscaler 29d cluster-autoscaler-operator 29d cluster-logging-metadata-reader 8d Expected results: # OCP4.2 $ oc version Client Version: openshift-clients-4.2-4-g33d97ed6 Server Version: 4.2.21 Kubernetes Version: v1.14.6+06eeef5 $ oc get clusterrolebinding.rbac -o wide | head NAME AGE ROLE USERS GROUPS SERVICEACCOUNTS alertmanager-main 4d2h ClusterRole/alertmanager-main openshift-monitoring/alertmanager-main amqstreams.v1.3.0-bvt4h-strimzi-cluster-operator-zjnd8 43h ClusterRole/amqstreams.v1.3.0-bvt4h kafka-dlaing/strimzi-cluster-operator basic-users 4d2h ClusterRole/basic-user system:authenticated cloud-credential-operator-rolebinding 4d2h ClusterRole/cloud-credential-operator-role openshift-cloud-credential-operator/default cluster-admin 4d2h ClusterRole/cluster-admin system:masters cluster-admins 4d2h ClusterRole/cluster-admin system:admin system:cluster-admins cluster-autoscaler 4d2h ClusterRole/cluster-autoscaler openshift-machine-api/cluster-autoscaler cluster-autoscaler-operator 4d2h ClusterRole/cluster-autoscaler-operator openshift-machine-api/cluster-autoscaler-operator cluster-logging-metadata-reader 2d13h ClusterRole/metadata-reader openshift-logging/logcollector Additional info:
It's a bug in how we serve data about clusterroles and roles, I've submitted a fix in https://github.com/kubernetes/kubernetes/pull/88897 I'll try to get that in k8s 1.18 and we'll get in ocp 4.5, moving accordingly.
This was fixed with k8s bump to 1.18, so moving to verification.
The issue has fixed: [root@dhcp-140-138 ~]# oc version Client Version: 4.5.0-202005072157-f415627 Server Version: 4.5.0-0.nightly-2020-05-08-200452 Kubernetes Version: v1.18.0-rc.1 [root@dhcp-140-138 ~]# oc get clusterrolebinding.rbac -o wide | head NAME ROLE AGE USERS GROUPS SERVICEACCOUNTS alertmanager-main ClusterRole/alertmanager-main 2m10s openshift-monitoring/alertmanager-main basic-users ClusterRole/basic-user 3h38m system:authenticated cloud-credential-operator-rolebinding ClusterRole/cloud-credential-operator-role 3h53m openshift-cloud-credential-operator/default cluster-admin ClusterRole/cluster-admin 3h54m system:masters ......
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-2020:2409