# Awx-projects-claim stuck in pending **URL:** \ **Category:** Get Help\ **Tags:** kubernetes, awx\ **Created:** [June 28, 2024, 11:14am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828 "2024-06-28T11:14:01Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [June 28, 2024, 11:14am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/1 "2024-06-28T11:14:01Z")
I have just upgraded AWX/Operator to 24.2.0/2.15.0 and everything went OK except the awx-projects-claim. This is stuck in pending: ```auto kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE awx-backup-claim Bound awx-backup-volume 4Gi RWO awx-backup-volume 9d postgres-15-ansible-awx-postgres-15-0 Bound pvc-d7e8181b-9492-4c97-a1a1-1c74ba714f20 8Gi RWO local-path 3h36m awx-projects-claim Pending awx-projects-volume 52m ``` The pv does exist: ```auto kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGE awx-postgres-13-volume 8Gi RWO Retain Released awx/postgres-13-awx-postgres-13-0 awx-postgres-volume 16d awx-projects-volume 2Gi RWO Retain Released awx/awx-projects-claim awx-projects-volume 16d awx-postgres-15-volume 8Gi RWO Retain Released awx/postgres-13-awx-postgres-13-0 awx-postgres-volume 16d awx-backup-volume 4Gi RWO Retain Bound awx/awx-backup-claim awx-backup-volume 9d pvc-d7e8181b-9492-4c97-a1a1-1c74ba714f20 8Gi RWO Delete Bound awx/postgres-15-ansible-awx-postgres-15-0 local-path 3h36m ``` The storage classes do too: ```auto kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 16d awx-projects-volume kubernetes.io/no-provisioner Delete WaitForFirstConsumer false 68s ``` I have tried modifying the pvc and pv files but I cannot get it to bind. I am sure that I am missing something obvious, but I can’t see it. Could someone point me in the right direction please? ---
**Author:** ![djyasin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/djyasin/32/114_2.png) [@djyasin](https://forum.ansible.com/u/djyasin)\ **Post date:** [July 3, 2024, 6:53pm UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/2 "2024-07-03T18:53:45Z")
Hello @bjwebster, we are so sorry to hear you’re having trouble! Could you provide us with the related Kubernetes logs? This will help us better understand what may be occurring here. Thank you for your time! ---
**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\ **Post date:** [July 3, 2024, 8:51pm UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/3 "2024-07-03T20:51:45Z")
Looks like you may need to set `projects_storage_class: local-path` in your `kind: AWX` spec. This may require you to manually delete the PVC for the operator to apply the change. ---
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [July 4, 2024, 7:45am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/4 "2024-07-04T07:45:03Z")
Denney-tech and djyasin, Thank you for your replies. I am on holiday at the moment with no access to my installation. I will follow-up with you when I get home early next week. ---
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [July 15, 2024, 7:46am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/5 "2024-07-15T07:46:22Z")
OK, here is the output from _kubectl describe pvc awx-projects-claim_: ```auto kubectl describe pvc awx-projects-claim Name: awx-projects-claim Namespace: awx StorageClass: local-path Status: Pending Volume: Labels: Annotations: Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Used By: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal WaitForFirstConsumer 3m6s (x97013 over 16d) persistentvolume-controller waiting for first consumer to be created before binding ``` ---
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [July 15, 2024, 7:54am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/6 "2024-07-15T07:54:10Z")
Denny-tech, My awx spec for project storage looks like this: ```auto projects_persistence: true projects_existing_claim: awx-projects-claim ``` Do I just need to add the line?: ```auto projects_persistence: true projects_existing_claim: awx-projects-claim projects_storage_class: local-path ``` The pending PVC already appear to be using local-path: ```auto kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE awx-backup-claim Bound awx-backup-volume 4Gi RWO awx-backup-volume 26d postgres-15-ansible-awx-postgres-15-0 Bound pvc-d7e8181b-9492-4c97-a1a1-1c74ba714f20 8Gi RWO local-path 17d awx-projects-claim Pending local-path 16d ``` ---
**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\ **Post date:** [July 15, 2024, 12:59pm UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/7 "2024-07-15T12:59:05Z")
@bjwebster Hi, You should specify `ReadWriteOnce` as the access mode for the PVC if you want to use `local-path`. The AWX Operator creates PVC for the project with the mode `ReadWriteMany` by default, which is not supported by `local-path` provisioner: [Persisting projects directory - Ansible AWX Operator Documentation](https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/persisting-projects-directory.html?h=access#persisting-projects-directory) Add following line to your awx spec and try again. ```yaml projects_storage_access_mode: ReadWriteOnce ``` ---
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [July 15, 2024, 2:05pm UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/8 "2024-07-15T14:05:46Z")
Kurokobo, Thank you for your help. I am not sure that I do want to use _local-path_, it just seems to be where I have ended up. I have been trying so many different thing over the past couple of weeks that I have got myself into a bit of a mess. It may be better if I just delete my installation and start again. I have used your awx-on-k3s guide to install previously but I want to access the AWX on its IP address rather than its hostname. The K3S server is running on an EC3 instance in AWS and is behind and API gateway and a Loadbalancer, which terminate HTTPS, so I don’t need certs on the AWX itself. What would be the best way to deploy AWX so that I can access it on the server’s node port? ---
**Author:** ![bjwebster](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bjwebster/32/3709_2.png) [@bjwebster](https://forum.ansible.com/u/bjwebster)\ **Post date:** [July 17, 2024, 10:13am UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/9 "2024-07-17T10:13:31Z")
I have re-installed AWX using the `awx-on-k3s` guide. I used the TLS option to make things simpler for myself. Everything is back up and running now so thank you to _kurokobu_ for providing such a comprehensive guide, and to _djyasin_ and _Denney-tech_ for their suggestions. ---
**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\ **Post date:** [July 17, 2024, 12:23pm UTC](https://forum.ansible.com/t/awx-projects-claim-stuck-in-pending/6828/10 "2024-07-17T12:23:32Z")
@bjwebster Thank you for the update, and I’m glad to hear that you’ve made progress despite my delayed response. I’m trying to answer your question for future reference. > [@bjwebster](#): > > What would be the best way to deploy AWX so that I can access it on the server’s node port? I believe “the best way” depends on your requirements. If you’re not particular about the PV provisioner, are fine with random passwords, and only need a single node, then deploying AWX with following minimal specs on K3s or Rancher should work good: ```yaml --- apiVersion: awx.ansible.com/v1beta1 kind: AWX metadata: name: awx-demo spec: service_type: nodeport nodeport_port: 30080 projects_persistence: true projects_storage_access_mode: ReadWriteOnce ``` Of course it’s also possible to change to use node port based on my guide. Simply remove the `awx-secret-tls` block from `kustomization.yaml` and specify `service_type` and `nodeport_*` instead of `ingress_*` in `awx.yaml` . Enjoy using AWX!