---
name: openshift-ts-storage-ocs-missing-pods
title: Why are no pods listed in the `openshift-storage` namespace?
description: 'There are no pods listed when you run the `oc get pods -n openshift-storage` command. When you view the `ibm-ocs-operator-controller-manager` logs with the `oc logs <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system` command, you see the following error message:'
last-updated: 2025-05-29
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why are no pods listed in the `openshift-storage` namespace?
{: #ts-ocs-no-pods}
{: support}


There are no pods listed when you run the `oc get pods -n openshift-storage` command. When you view the `ibm-ocs-operator-controller-manager` logs with the `oc logs <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system` command, you see the following error message:
{: tsSymptoms}

```sh
Failed to get StorageCluster","error":"no matches for kind \"StorageCluster\" in version \"ocs.openshift.io/v1\
```
{: screen}


The catalog source for your ODF storage cluster is unhealthy.
{: tsCauses}

Remove all the catalog sources from your cluster.
{: tsResolve}

1. Remove all catalog sources from your cluster. A new catalog source and pods automatically generate.
    ```sh
    oc -n openshift-marketplace delete catsrc --all
    ```
    {: pre}

2. Wait a few minutes and verify that the pods regenerate. If the pods regenerate, the ODF installation proceeds. If the pods don't regenerate, [contact ODF support by raising a case in the Red Hat customer portal](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-error-unresolved&format=markdown).
    ```sh
    oc get pods,catsrc -n openshift-marketplace
    ```
    {: pre}