<p>For those that are interested, I have yet to find a resolution for this problem. I simply created a github account, and that works for Ansible automation.</p>

CC BY-SA 4.0
2023-06-24T05:16:37.013Z
2023-06-24T05:16:37.013Z
marshit
<p>I have a strange issue that has me racking my brain. I have installed AWX 22.3.0 onto Ubuntu 22.04.1-Ubuntu at least three times now. Let me make sure I get everything to those reading this.</p>
<p>I have followed many whitepapers, directions, and videos, and for the life of me, I can't figure out why I can't get any playbooks using,.yaml or.yml in the <code>/var/lib/awx/projects/</code> to appear within &quot;Base Project Path&quot;. I continue to receive the message below:</p>
<pre><code>There are no available playbook directories in /var/lib/awx/projects. Either that directory is empty or all of its contents are already assigned to other projects. Create a new directory there and make sure the playbook files can be read by the &quot;awx&quot; system user, or have AWX directly retrieve your playbooks from source control using the Source Control Type option above.
</code></pre>
<p>I'm using K3S Kubernetes, and my pods are all active and working.</p>
<p>I have edited my &quot;awx-web&quot; to make sure it has the <code>/var/lib/awx/projects</code> path as the</p>
<pre><code>kubectl exec -ti deploy/awx-web -c awx-web -- /bin/bash
</code></pre>
<p>env</p>
<pre><code>export PROJECTS_ROOT=&quot;/new/path/to/projects&quot;
</code></pre>
<p>All of it looks good. I deleted and recreated the pod after the change as well. But the ROOT path was already there originally, as I expected based on how I installed it.</p>
<p>Hopefully, that is enough for people to help me with my problem. I'm just at a loss and don't know what else it could be at this point. I mean, do I need to open firewall ports? I just don't know.</p>
<p>Also, the permissions are below after I did a <code>mkdir -P</code> and manually created a <code>/var/lib/awx/projects/playbooks</code> directory. Then I created a YAML file.</p>
<p>Maybe it could be permission as well; who knows?</p>

<kubernetes><ubuntu><awx>
Unable to see manually created playbooks in AWX
marshit
# Unable to see manually created playbooks in AWX

(Asked by: username_0 on 2023-06-20)

I have a strange issue that has me racking my brain. I have installed AWX 22.3.0 onto Ubuntu 22.04.1-Ubuntu at least three times now. Let me make sure I get everything to those reading this.
I have followed many whitepapers, directions, and videos, and for the life of me, I can't figure out why I can't get any playbooks using,.yaml or.yml in the /var/lib/awx/projects/ to appear within "Base Project Path". I continue to receive the message below:
There are no available playbook directories in /var/lib/awx/projects. Either that directory is empty or all of its contents are already assigned to other projects. Create a new directory there and make sure the playbook files can be read by the "awx" system user, or have AWX directly retrieve your playbooks from source control using the Source Control Type option above.

I'm using K3S Kubernetes, and my pods are all active and working.
I have edited my "awx-web" to make sure it has the /var/lib/awx/projects path as the
kubectl exec -ti deploy/awx-web -c awx-web -- /bin/bash

env
export PROJECTS_ROOT="/new/path/to/projects"

All of it looks good. I deleted and recreated the pod after the change as well. But the ROOT path was already there originally, as I expected based on how I installed it.
Hopefully, that is enough for people to help me with my problem. I'm just at a loss and don't know what else it could be at this point. I mean, do I need to open firewall ports? I just don't know.
Also, the permissions are below after I did a mkdir -P and manually created a /var/lib/awx/projects/playbooks directory. Then I created a YAML file.
Maybe it could be permission as well; who knows?

**Tags:** kubernetes, ubuntu, awx


---

## 1 answers

### Answer by username_0 on 2023-06-24. Score: 1

For those that are interested, I have yet to find a resolution for this problem. I simply created a github account, and that works for Ansible automation.


---

