> For the complete documentation index, see [llms.txt](https://aizen-corp.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aizen-corp.gitbook.io/docs/troubleshooting/installation-issues.md).

# Installation Issues

This section provides recommended solutions to some commonly seen problems during deployment:

* [#unable-to-pull-images-from-the-aizen-repository](#unable-to-pull-images-from-the-aizen-repository "mention")
* [#pods-in-a-failed-state](#pods-in-a-failed-state "mention")
* [#no-space-left-on-device](#no-space-left-on-device "mention")

## Unable to Pull Images From the Aizen Repository

### Error: ImagePullBackOff or ErrImagePull

ImagePullBackOff will be seen when you describe the pod using the command:

{% code overflow="wrap" %}

```
kubectl describe pod <PODNAME>

kubectl get pods -n <NAMESPACE>
```

{% endcode %}

### Solution

1. Check if the Aizen Repository secret name used during deployment is missing in your namespace, or if the Aizen Repository credential name was misspelled during deployment:

   <pre data-overflow="wrap"><code>kubectl get secrets -n &#x3C;NAMESPACE>
   </code></pre>
2. If the names are missing, create them by running this command:

   <pre data-overflow="wrap"><code>kubectl create secret docker-registry aizenrepo-creds 
   --docker-username=aizencorp 
   --docker-password=&#x3C;YOUR SECRET> 
   -n &#x3C;NAMESPACE>
   </code></pre>

## Pods in a Failed State

1. When the state of specified pods is not in a *Running* state, run this command:

   <pre data-overflow="wrap"><code>kubectl -n &#x3C;NAMESPACE> get pods
   </code></pre>
2. Check the describe output for the pod:

   <pre data-overflow="wrap"><code>kubectl -n &#x3C;NAMESPACE> describe pod &#x3C;PODNAME>
   </code></pre>

## No Space Left on Device

### Error: No space left on device

This error is seen during the execution of console commands.

### Solution

1. Validate that the storage class has the property ALLOWVOLUMEEXPANSION set to true:

   <pre data-overflow="wrap"><code>kubectl describe sc &#x3C;storage classname>
   </code></pre>
2. Increase the storage size for the PersistentVolumeClaim (PVC) without any downtime:

   <pre data-overflow="wrap"><code>kubectl get pvc -n &#x3C;namespace>
   </code></pre>
3. Edit the storage size of the PVC:

   <pre data-overflow="wrap"><code>kubectl edit pvc &#x3C;pvc name> -n &#x3C;namespace>
   </code></pre>

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Edit and increase the storage size for all the PVCs listed by the previous command.</p></div>
4. Delete the storage StatefulSet:

   <pre data-overflow="wrap"><code>kubectl -n &#x3C;namespace> get statefulset
    
   kubectl delete statefulset --cascade=orphan &#x3C;statefulset name> -n namespace
   </code></pre>
5. Redeploy the chart to re-create storage StatefulSet:

   <pre data-overflow="wrap"><code>helm upgrade &#x3C;existing release name> &#x3C;chartname> -n &#x3C;>namespace>
   </code></pre>
6. The storage StatefulSet will be created with the updated PVC size:

   <pre data-overflow="wrap"><code>kubectl -n &#x3C;namespace> get pvc
   </code></pre>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aizen-corp.gitbook.io/docs/troubleshooting/installation-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.