---
name: openshift-ts-storage-file-addon-cm
title: Why is the File Storage for VPC add-on in `Critical` state
description: Troubleshoot file storage add-on ConfigMap issues.
last-updated: 2026-08-25
---

> ## 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 is the File Storage for VPC add-on in `Critical` state
{: #ts-storage-file-addon-cm}

When you list add-ons or check the File Storage for VPC add-on status configmap, you see errors similar to the following.
{: tsSymptoms}


Troubleshoot file storage add-on ConfigMap issues.
{: shortdesc}

```txt
Unable to set 'bmf' as default storage class due to internal error.
event: Change default storage class request
```
{: screen}

```txt
'EnableVPCFileCSIDriver unsuccessful, Error: resource name may not be empty, DriverVersion: v2.0.13'
```
{: screen}


The `addon-vpc-file-csi-driver-configmap` has missing or incorrect values.
{: tsCauses}

Review `file-csi-driver-status` configmap for errors and update any missing or incorrect values in the `addon-vpc-file-csi-driver-configmap` configmap.
{: tsResolve}


1. Review the add-on status.
    ```sh
    ibmcloud ks cluster addon ls --cluster <cluster>
    ```
    {: pre}

1. Review the events in the file status configmap.
    ```sh
    oc get cm file-csi-driver-status -n kube-system -o yaml
    ```
    {: pre}

    Example output
    ```yaml
    apiVersion: v1
    data:
      EIT_ENABLED_WORKER_NODES: ""
      PACKAGE_DEPLOYER_VERSION: ""
      SET_DEFAULT_STORAGE_CLASS: ""
      events: |
        - description: Unable to set 'bmf' as default storage class due to internal error.
          event: Change default storage class request
          timestamp: "2025-06-26 14:07:53"
        - description: 'EnableVPCFileCSIDriver unsuccessful, Error: resource name may not
            be empty, DriverVersion: v2.0.13'
          event: EnableVPCFileCSIDriver
          timestamp: "2025-06-26 14:07:53"
    ```

1. Get the storage operator logs.
    ```sh
    kubectl logs ibm-storage-operator-xxx -n kube-system
    ```
    {: pre}

1. If any property is missing or invalid, edit the value in the configmap.
    ```sh
    kubectl edit cm addon-vpc-file-csi-driver-configmap  -n kube-system -o yaml
    ```
    {: pre}

1. After 5-10 mins check the add-on status.
    ```sh
    ibmcloud ks cluster addon ls --cluster <cluster>
    ```
    {: pre}

1. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.