IBM Cloud Docs
Debugging the Cloud Object Storage add-on

Debugging the Cloud Object Storage add-on

Virtual Private Cloud Classic infrastructure

The ibm-object-csi-driver add-on does not run properly.

Follow these steps to gather gather details about the issue.

  1. Pull the cluster configuration.
    ibmcloud ks cluster config -c <cluster_name/cluster_id>
  2. Check the health of the add-on to ensure it is deployed properly.
    ibmcloud ks cluster addon ls --cluster <cluster_name/cluster_id>
  3. Check the version of the installed add-on. It is recommended to use the latest version for better support.
    ibmcloud ks cluster addon ls --cluster <cluster_name/cluster_id> | grep ibm-object-csi-driver
  4. Make sure that all CSI driver pods are in running state.
    kubectl get pods -n ibm-object-csi-operator | grep ibm-object-csi

If any CSI driver pod is in ImagePullBackOff state, that means the image used for pods creation is not available in the registry or there might be permission issues. Gather the output from the previous steps and, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.

If any CSI driver pod is in CrashLoopBackOff state, you can try the following steps:

  1. Describe that pod.

    kubectl describe pod ibm-ibm-object-csi-xxx -n ibm-object-csi-operator

  2. Look for the container that is continuously restarting.

  3. Collect logs for more details.

    kubectl logs ibm-ibm-object-csi-xxx -n ibm-object-csi-operator

  4. Upgrade the add-on to the latest version for a possible fix.

  5. If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.

If you need to contact support for further help, make sure you gather the following details for the support ticket.

  • Add-on health status and add-on version mentioned above.

  • PVC describe

    kubectl describe pvc <PVC-NAME> -n <PVC-NAMESPACE>

  • PV describe

    kubectl describe pv <pv-name>

  • Pod describe

    kubectl describe pod <POD-NAME> -n <POD-NAMESPACE>

  • Logs of controller-manager pod

    kubectl logs ibm-ibm-object-csi-operator-controller-manager-xxx -n ibm-object-csi-operator

  • Logs of csi-node pod

    kubectl logs ibm-object-csi-node-xxx -n ibm-object-csi-operator