checked with the pr , can't reproduce the issue now: [root@localhost oc]# ./oc completion bash >new_oc_bash [root@localhost oc]# source new_oc_bash [root@localhost oc]# ./oc get Display all 193 possibilities? (y or n) alertmanagerconfigs.monitoring.coreos.com kubecontrollermanagers.operator.openshift.io alertmanagers.monitoring.coreos.com kubeletconfigs.machineconfiguration.openshift.io apirequestcounts.apiserver.openshift.io kubeschedulers.operator.openshift.io
*** Bug 2110359 has been marked as a duplicate of this bug. ***
oc version Client Version: 4.11.0-0.nightly-2022-08-12-000313 Kustomize Version: v4.5.4 [root@localhost ~]# oc completion bash >new_oc_bash [root@localhost ~]# source new_oc_bash [root@localhost ~]# oc get Display all 201 possibilities? (y or n) alertmanagerconfigs.monitoring.coreos.com kubestorageversionmigrators.operator.openshift.io alertmanagers.monitoring.coreos.com leases.coordination.k8s.io apirequestcounts.apiserver.openshift.io limitranges 。。。
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 (Moderate: OpenShift Container Platform 4.11.1 bug fix and security update), 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/RHSA-2022:6103