Description of problem: oc adm inspect ns/exist ns/nonexist command fails without collection any data from the existed resources by throwing resource not found error. How reproducible: Run oc adm release inspect with not existed resources Actual results: It fails without inspecting existed resources Expected results: It should continue inspection and can return a warning message about not existed resources.
the issue has fixed : oc adm inspect clusteroperator/openshift-apiserver clusteroperator/kube-apiservernoexit Gathering data for ns/openshift-config... Gathering data for ns/openshift-config-managed... Gathering data for ns/openshift-apiserver-operator... Gathering data for ns/openshift-apiserver... Gathering data for ns/openshift-etcd-operator... Wrote inspect data to inspect.local.5693469870155877677. error: errors occurred while gathering data: [clusteroperators.config.openshift.io "kube-apiservernoexit" not found, skipping gathering namespaces/openshift-config due to error: the server doesn't have a resource type "egressfirewalls", skipping gathering namespaces/openshift-config-managed due to error: the server doesn't have a resource type "egressfirewalls", skipping gathering namespaces/openshift-apiserver-operator due to error: the server doesn't have a resource type "egressfirewalls", skipping gathering namespaces/openshift-apiserver due to error: the server doesn't have a resource type "egressfirewalls", skipping gathering namespaces/openshift-etcd-operator due to error: the server doesn't have a resource type "egressfirewalls", skipping gathering endpoints/host-etcd-2 due to error: endpoints "host-etcd-2" not found] [root@localhost ~]# echo $? 1 oc version --client Client Version: 4.11.0-202205170307.p0.g2e3d4ac.assembly.stream-2e3d4ac Kustomize Version: v4.5.4
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 (Important: OpenShift Container Platform 4.11.0 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:5069