Bug 1810848
Summary: | '-o wide' option does not work well | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | shishika |
Component: | oc | Assignee: | Maciej Szulik <maszulik> |
Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.0 | CC: | aos-bugs, jokerman, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:18:46 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: | |
Embargoed: |
Description
shishika
2020-03-06 02:18:46 UTC
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 |