You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Troubleshoot common problems with Azure Container Storage, including installation and storage pool issues.
4
4
author: khdownie
5
5
ms.service: azure-container-storage
@@ -8,7 +8,7 @@ ms.author: kendownie
8
8
ms.topic: how-to
9
9
---
10
10
11
-
# Troubleshoot Azure Container Storage Preview
11
+
# Troubleshoot Azure Container Storage preview
12
12
13
13
[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. Use this article to troubleshoot common issues with Azure Container Storage and find resolutions to problems.
14
14
@@ -71,6 +71,57 @@ Because ephemeral disks (local NVMe and Temp SSD) are ephemeral and not durable,
71
71
72
72
If you need a persistent volume, where the volume has a lifecycle independent of any individual pod that's using the volume, Azure Container Storage supports replication for NVMe. You can create a storage pool with replication and create persistent volumes from there. See [Create storage pool with volume replication](use-container-storage-with-local-nvme-replication.md) for guidance. Note that because ephemeral disk storage pools consume all the available NVMe disks, you must delete any existing ephemeral disk storage pools before creating a new storage pool with replication enabled. If you don't need persistence, you can create a generic ephemeral volume.
73
73
74
+
### Pod pending creation due to ephemeral volume size above available capacity
75
+
76
+
An ephemeral volume is allocated on a single node. When you configure the size of ephemeral volumes for your pods, the size should be less than the available capacity of a single node's ephemeral disk. Otherwise, the pod creation will be in pending status.
77
+
78
+
Use the following command to check if your pod creation is in pending status.
79
+
80
+
```output
81
+
$ kubectl get pods
82
+
NAME READY STATUS RESTARTS AGE
83
+
fiopod 0/1 Pending 0 17s
84
+
```
85
+
86
+
In this example, the pod `fiopod` is in `Pending` status.
87
+
88
+
Use the following command to check if the pod has the warning event for persistentvolumeclaim creation.
89
+
90
+
```output
91
+
$ kubectl describe pod fiopod
92
+
...
93
+
Events:
94
+
Type Reason Age From Message
95
+
---- ------ ---- ---- -------
96
+
Warning FailedScheduling 40s default-scheduler 0/3 nodes are available: waiting for ephemeral volume controller to create the persistentvolumeclaim "fiopod-ephemeralvolume". preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
97
+
```
98
+
99
+
In this example, the pod shows the warning event on creating persistent volume claim `fiopod-ephemeralvolume`.
100
+
101
+
Use the following command to check if the persistent volume claim fails to provision due to insufficient capacity.
102
+
103
+
```output
104
+
$ kubectl describe pvc fiopod-ephemeralvolume
105
+
...
106
+
Warning ProvisioningFailed 107s (x13 over 20m) containerstorage.csi.azure.com_aks-nodepool1-29463073-vmss000000_7f5bd88d-be76-40d2-a59e-e51ce000e35e failed to provision volume with StorageClass "acstor-ephemeraldisk-temp": rpc error: code = Internal desc = Operation failed: GenericOperation("error in response: status code '507 Insufficient Storage', content: 'RestJsonError { details: \"Operation failed due to insufficient resources: Not enough suitable pools available, 0/1\", message: \"SvcError :: NotEnoughResources\", kind: ResourceExhausted }'")
107
+
```
108
+
109
+
In this example, `Insufficient Storage` is shown as the reason for volume provisioning failure.
110
+
111
+
Run the following command to check the available capacity of a single node's ephemeral disk.
In this example, the available capacity of temp disk for a single node is `75031990272` bytes or 69 GiB.
122
+
123
+
Adjust the volume storage size below available capacity and re-deploy your pod. See [Deploy a pod with a generic ephemeral volume](use-container-storage-with-temp-ssd.md#3-deploy-a-pod-with-a-generic-ephemeral-volume).
0 commit comments