# Execution Nodes capacity not showing properly? **URL:** \ **Category:** AWX Project\ **Tags:** awx, kubernetes\ **Created:** [May 23, 2023, 7:52pm UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027 "2023-05-23T19:52:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![picodon](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/picodon/32/3592_2.png) [@picodon](https://forum.ansible.com/u/picodon)\ **Post date:** [May 23, 2023, 7:52pm UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/1 "2023-05-23T19:52:31Z")
Hi, I have deployed several Execution Nodes which are all 4 cpus and 16GB but they all show as 0.5 cpu and 2GB in terms of capacity in AWX, which seriously limits their workload! How can we allocate the full host’s specs (4cpu/16ram) to the exec. node so that it properly reports back the available capacity to the Control Planes? I was able to adjust on the task container specs on the Kubernetes side (even tho rsyslog\_resources still creates an error on my end) but still cannot fix the exec. nodes… Thanks! ---
**Author:** ![Anh\_Nguyen](https://avatars.discourse-cdn.com/v4/letter/a/e47774/32.png) [@Anh\_Nguyen](https://forum.ansible.com/u/Anh_Nguyen)\ **Post date:** [May 24, 2023, 10:42am UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/2 "2023-05-24T10:42:21Z")
That’s Container not your host machine? ---
**Author:** ![picodon](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/picodon/32/3592_2.png) [@picodon](https://forum.ansible.com/u/picodon)\ **Post date:** [May 24, 2023, 3:16pm UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/3 "2023-05-24T15:16:24Z")
Execution nodes are host machines (running jobs using ansible-runner and podman) completely outside (and far from) the Kubernetes cluster (AWX control planes). My issue is they don’t report their fulls specs to AWX control planes (reporting 0.5 cpu instead of 4 for example), which limits their usage… I wonder if it’s how podman is run by ansible-runner or something else in the receptor/ansible-runner? ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [May 24, 2023, 7:40pm UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/4 "2023-05-24T19:40:32Z")
JC AWX is getting those cpu/mem measurements by running ansible-runner worker --worker-info you can ssh into those machines, change to awx user, and run that command above. If you want to look deeper into those who values are obtained, here is the source code [https://github.com/ansible/ansible-runner/blob/0746379fbf31c357a75946183b23dda06ea777f8/src/ansible\_runner/utils/capacity.py#L8](https://github.com/ansible/ansible-runner/blob/0746379fbf31c357a75946183b23dda06ea777f8/src/ansible_runner/utils/capacity.py#L8) Let us know if that helps a bit AWX Team ---
**Author:** ![picodon](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/picodon/32/3592_2.png) [@picodon](https://forum.ansible.com/u/picodon)\ **Post date:** [May 24, 2023, 9:38pm UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/5 "2023-05-24T21:38:33Z")
Hey, I found the problem! I did check ansible-runner infos and it was showing the right specs for the exec. nodes matching the hardware. BUT, after testing and confirming, the resources requirements that are set for the k8s task container are ALSO applied to the podman containers running on the exec. nodes! I edited the deployment’s resources and applied, after a new health check the exec. nodes now show the new limitations. I think it’s not best because the exec. nodes can potentially use much more resources than what we want to allocate/limit on our awx\_task container(s) for the Control Planes. It would be great to ensure that podman on the exec. node side doesn’t get limited by awx\_task container’s resources limits, or that exec. nodes get their own limitations. Thanks! ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [May 26, 2023, 4:03am UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/6 "2023-05-26T04:03:05Z")
oh this is an interesting finding and is a bug I believe. I will put up a bug report AWX Team ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [May 26, 2023, 4:08am UTC](https://forum.ansible.com/t/execution-nodes-capacity-not-showing-properly/38027/7 "2023-05-26T04:08:26Z")
tracking here [https://github.com/ansible/awx/issues/14051](https://github.com/ansible/awx/issues/14051)