// Module included in the following assemblies:
//
// storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc

:_mod-docs-content-type: PROCEDURE
[id="investigating-a-pvc-stuck-in-the-pending-state_{context}"]
= Investigating a PVC stuck in the Pending state

[role="_abstract"]
Investigate persistent volume claims (PVCs) stuck in a `Pending` state to determine whether the cause is insufficient resources, network problems, mismatched storage classes, or unavailable persistent volumes (PVs).

A persistent volume claim (PVC) can get stuck in the `Pending` state for the following reasons:

* Insufficient computing resources.
* Network problems.
* Mismatched storage class or node selector.
* No available persistent volumes (PVs).
* The node with the PV is in the `Not Ready` state.

.Prerequisites
* You have installed the {oc-first}.
* You have logged in to the {oc-first} as a user with `cluster-admin` permissions.

.Procedure
. Retrieve the list of PVCs by running the following command:
+
[source,terminal]
----
$ oc get pvc
----
+
.Example output
[source,terminal]
----
NAME        STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
lvms-test   Pending                                      lvms-vg1       11s
----

. Inspect the events associated with a PVC stuck in the `Pending` state by running the following command:
+
[source,terminal]
----
$ oc describe pvc <pvc_name>
----
+
Replace `<pvc_name>` with the name of the PVC. For example, `lvms-vg1`.
+
.Example output
[source,terminal]
----
Type     Reason              Age               From                         Message
----     ------              ----              ----                         -------
Warning  ProvisioningFailed  4s (x2 over 17s)  persistentvolume-controller  storageclass.storage.k8s.io "lvms-vg1" not found
----