# How to: Troubleshooting openebs-localpv-provisioner Failures in kURL

**URL:** <https://community.replicated.com/t/how-to-troubleshooting-openebs-localpv-provisioner-failures-in-kurl/1520>\
**Category:** How do I?\
**Tags:** support, kurl\
**Created:** [May 15, 2025, 6:42am UTC](https://community.replicated.com/t/how-to-troubleshooting-openebs-localpv-provisioner-failures-in-kurl/1520 "2025-05-15T06:42:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dexter\_Yan](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dexter_yan/32/661_2.png) [@Dexter\_Yan](https://community.replicated.com/u/Dexter_Yan)\
**Post date:** [May 15, 2025, 6:42am UTC](https://community.replicated.com/t/how-to-troubleshooting-openebs-localpv-provisioner-failures-in-kurl/1520/1 "2025-05-15T06:42:18Z")

</div>

After installing your kURL cluster, you might encounter an issue where the `openebs-localpv-provisioner` pod keeps failing or restarting. Consequently, related Persistent Volume Claims (PVCs) remain in the `Pending `state without being bound to any volume.

Before taking any recovery or cluster reset actions, it is recommended to first collect relevant diagnostic information about the `openebs-localpv-provisioner` pod. This will help you identify the root cause and take appropriate steps.

**1. Collect Logs from the openebs-localpv-provisioner Pod**  
Run the following commands to describe the pod and collect its logs:

```auto
kubectl describe pod <openebs-localpv-provisioner-pod>
kubectl logs <openebs-localpv-provisioner-pod>

```

Look for errors that may indicate issues with the underlying host disk or other system factors.

**2. Check the Status of the init-pvc-xxxxx Pod**  
Use the following command to check the status of the initialization pod associated with the PVC:

```auto
kubectl describe pod init-pvc-xxxxx

```

If this pod is not marked as Completed, it indicates that the PVC binding process has failed. Inspect the pod logs for more details on the failure.

**3. Verify File Permissions in the /var/openebs Directory**  
Ensure that the permissions on the target directory are correct:

```auto
ls -ld /var/openebs

```

A correct example of the directory permissions should look like:

```auto
drwxr-xr-x

```

**4. Collect a Host Support Bundle (if necessary)**  
To assist further troubleshooting, collect a host support bundle and share it with the Replicated support team for detailed analysis.
