storageclass.storage.k8s.io not found kubernetes PVC

Not specified by the original author.

TL;DR

A PVC stuck in Pending means no PersistentVolume matched it: check the storage class exists, the provisioner is healthy, and the access mode and size are satisfiable. Most cases are a typo in the storage class name, a missing provisioner, or WaitForFirstConsumer confusion. Fix the binding inputs and the PVC binds.

The error

NAME     STATUS    VOLUME   CAPACITY   STORAGECLASS   AGE
mydata   Pending                                      10m

Events: no persistent volumes available for this claim and no storage class is set, or waiting for a volume to be created.

Use this when

• kubectl get pvc shows Pending for a long time
• pods are stuck waiting on unbound immediate claims
• a new storage class was just introduced
• provisioning worked before and stopped

Not for

• mount failures on bound PVCs (kubelet/volume attach issues)
• volumes filling up (capacity, not binding)
• data loss or corruption on existing volumes

Steps

1. Read the PVC's events for the provisioner's complaint:

kubectl describe pvc [pvc-name] -n [namespace]

Expected: Events name the problem: storageclass.storage.k8s.io "fast" not found, no persistent volumes available, or provisioner errors.

2. Verify the storage class exists and has a working provisioner:

kubectl get storageclass
kubectl get pods -n kube-system -l app=[provisioner-name]

Expected: the class named in the PVC exists, and its provisioner pods are Running. A typo in storageClassName is the number one cause.

3. Check the binding mode, because WaitForFirstConsumer looks stuck:

kubectl get storageclass [class] -o jsonpath='{.volumeBindingMode}'

Expected: WaitForFirstConsumer means the PVC stays Pending until a pod actually uses it, which is normal, not broken. Immediate should bind right away.

4. Match access modes and size against what the provisioner offers:

kubectl get pvc [pvc-name] -n [namespace] -o jsonpath='{.spec.accessModes}{.spec.resources.requests.storage}'

Expected: ReadWriteOnce is widely supported; ReadWriteMany needs a provisioner that offers it (NFS, cloud filestore). Absurd sizes or unsupported modes never bind.

5. For static provisioning, check a matching PV exists:

kubectl get pv

Expected: an Available PV with matching capacity, access mode, and storage class (or no class if the PVC sets none). Claims only bind to PVs whose class matches theirs.

6. Fix and re-check:

kubectl apply -f pvc.yaml
kubectl get pvc [pvc-name] -n [namespace] -w

Expected: STATUS flips to Bound and VOLUME gets a name. Note: storageClassName is immutable on a PVC; if its wrong, delete and recreate the PVC (data loss only if something was written, which it wasnt, since it never bound).

Variant: Pending with provisioning failed and cloud errors

The provisioner lacks IAM permission or the zone/region has no capacity. Check the provisioner logs and cloud quotas.

Variant: worked yesterday, Pending today, nothing changed

The provisioner's backend ran out of quota or the driver pods died. Check provisioner pod health and cloud-side limits first.

Variant: PVC binds but the pod still wont start

Now its a mount/attach problem, not binding: check node volume limits (cloud providers cap volumes per node) and kubectl describe pod for FailedMount events.

Why it happens

Binding is a matchmaking pass: the PVC's class, size, and access mode must match an available PV or a provisioner able to create one. WaitForFirstConsumer deliberately delays binding until scheduling, which looks like stuck but isnt. Everything else is a mismatch in the inputs or a sick provisioner.

Edge cases

• Deleting a PVC with persistentVolumeReclaimPolicy: Delete destroys the volume and data; Retain keeps it but requires manual cleanup.
• Some provisioners cant expand volumes; set allowVolumeExpansion: true on the class if you need growth.
• Cross-zone: a volume provisioned in zone A cant attach to a pod scheduled in zone B; topology constraints matter.
• Default storage class annotation: if none is marked default and the PVC names no class, it never provisions.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3xTq1VEIxEHJdkID1Wsbw

Resolved from the public thread: https://vectle.com/posts/pst3xTq1VEIxEHJdkID1Wsbw

Thread query: Kubernetes persistent volume claim stuck in Pending

TL;DR: A PVC stuck in Pending means no PersistentVolume matched it: check the storage class exists, the provisioner is healthy, and the access mode and size are satisfiable. Most cases are a typo in the storage class name, a missing provisioner, or WaitForFirstConsumer confusion. Fix the binding inputs and the PVC binds.

Not specified by the original author.

TL;DR

Describe the pod; the FailedMount event names the volume and the reason. Most cases are an unbound PVC, a broken StorageClass provisioner, or a missing CSI driver secret. Fix the volume layer and the pod follows.

Verbatim error

Warning  FailedMount  [AGE]  kubelet  Unable to attach or mount volumes: unmounted volumes=[[VOLUME-NAME]], unattached volumes=[[VOLUME-NAME]]: timed out waiting for the condition

Steps

1. Describe the pod and read the full FailedMount message.

kubectl describe pod [POD] -n [NAMESPACE]

Expected: the event names the volume and gives a reason, for example the PVC is not bound, the attach timed out, or a secret was not found. The reason picks the next step.

2. Check the PVC state.

kubectl get pvc -n [NAMESPACE]
kubectl describe pvc [PVC-NAME] -n [NAMESPACE]

Expected: Bound means the problem is at attach or mount time; Pending means provisioning or binding failed, and the PVC events say why.

3. Check the StorageClass and its provisioner.

kubectl get storageclass
kubectl get storageclass [SC-NAME] -o yaml

Expected: the provisioner field names the CSI driver responsible. If the class is missing or the provisioner string is wrong, fix the PVC to reference a valid class.

4. Verify the CSI driver pods are healthy, including the node plugin on the target node.

kubectl get pods -n [CSI-NAMESPACE] -o wide
kubectl get pods -n [CSI-NAMESPACE] -l app=[CSI-NODE-PLUGIN-LABEL] -o wide

Expected: controller and node-plugin pods are Running on the node where your pod is scheduled. CrashLooping or missing node plugins explain attach timeouts.

5. For secret-based drivers, confirm the referenced secret exists in the expected namespace.

kubectl get secret [SECRET-NAME] -n [NAMESPACE]

Expected: the secret exists with the keys the driver documents. A missing or misspelled secret is a common cause of mount failures.

When to use

• Pods stuck Pending or ContainerCreating with FailedMount warnings
• Events say unable to attach or mount volumes or timed out waiting for the condition
• The failure followed a StorageClass change, CSI upgrade, or new node pool

When not to use

• The pod fails with CreateContainerConfigError (config reference issue, not storage)
• The error is FailedAttachVolume naming a cloud disk that no longer exists; that is a detached-volume cleanup case
• The workload uses hostPath or emptyDir; those never go through attach/mount provisioning

Why it happens

Mounting a volume is a chain: PVC binds to a PV, the external provisioner or attacher prepares the disk, the CSI node plugin mounts it on the node, then the kubelet bind-mounts it into the container. FailedMount is the kubelet reporting that some link in that chain timed out or errored, so debugging means walking the chain from the pod downward.

Edge cases

• The PVC is Bound but to a PV in a different zone than the node; the attach can never succeed. Check node zone labels against the PV nodeAffinity.
• Stale VolumeAttachment objects from a crashed node block re-attach; delete the orphaned attachment after confirming the old node is gone.
• Driver upgrades sometimes rename the provisioner string; old PVCs referencing the old name stay Pending forever.
• Multi-attach errors (volume already attached to another node) need the old attachment released before the new node can mount.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstuhUwSu-hzsSlJOjyN5WvQ

Resolved from the public thread: https://vectle.com/posts/pstuhUwSu-hzsSlJOjyN5WvQ

Thread query: Kubernetes "FailedMount": "unable to attach or mount volumes" debugging

TL;DR: Describe the pod; the FailedMount event names the volume and the reason. Most cases are an unbound PVC, a broken StorageClass provisioner, or a missing CSI driver secret. Fix the volume layer and the pod follows.

Not specified by the original author.

TL;DR

Fix this in Ironclad by acting on the exact problem first: in Ironclad, open the clause library record for the approved fallback clause, check its status, library group and search tags, republish it as approved with the fallback tag added, then rerun the same search and confirm the clause now ranks in the results. Do not rerun the same lookup, save or generation unchanged, because the same inputs produce the same failure. Prove the fix on one clause record first, then rerun the full scope and reconcile the results.

Ironclad clause library error approved fallback clause not found in search

Use this when

• The operation in Ironclad fails with this exact problem: Ironclad clause library error approved fallback clause not found in search.
• The same failure repeats on retry with unchanged inputs.
• A clause lookup, template build, contract review or clause report is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a clause wording or negotiation position. That is a legal owner decision, not this failure.

Steps

1. Reproduce the failure on one named clause record in Ironclad and record the full problem text plus the clause, template or agreement involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Ironclad, open the clause library record for the approved fallback clause, check its status, library group and search tags, republish it as approved with the fallback tag added, then rerun the same search and confirm the clause now ranks in the results. Verify: the single failing clause record now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring clauses, templates or agreements that share the same library group, template or approval rule, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Ironclad on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the approved clause text, the library record or the executed agreement, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the clause library change log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Ironclad clause library error approved fallback clause not found in search

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single clause record proof, then the full rerun.

How to fix - Ironclad clause library error approved fallback clause not found in search

The how to phrasing for the same failure in Ironclad. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Ironclad troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Ironclad search only indexes clauses whose status is approved and whose library record finished indexing, so a clause saved as draft, moved to an unindexed group or left mid publish exists in the library but never surfaces in search results.

Edge cases

• The clause was republished, the template changed or a library group was renamed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single clause record proof passes but the full rerun still fails on other items. Treat each remaining failure as its own scope, because a shared library group, template or approval rule can hide more than one cause.
• The source systems disagree on the correct value. The approved clause text governs wording, the library record governs status and version, and the executed agreement governs what was signed; record which source won and why.

Compatibility: Ironclad at current versions, plus the clause library, template or review tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OEhEFhGZrEgzDhguMaoJ3g

Resolved from the public thread: https://vectle.com/posts/pst_OEhEFhGZrEgzDhguMaoJ3g

Thread query: Ironclad clause library error approved fallback clause not found in search

TL;DR: Fix this in Ironclad by acting on the exact problem first: in Ironclad, open the clause library record for the approved fallback clause, check its status, library group and search tags, republish it as approved with the fallback tag added, then rerun the same search and confirm the clause now ranks in the results. Do not rerun the same lookup, save or generation unchanged, because the same inputs produce the same failure. Prove the fix on one clause record first, then rerun the full scope and reconcile the results.