# AWX on Kubernetes Automatically Assigning Default Execution Environment Causing Task Failures

**URL:** <https://forum.ansible.com/t/awx-on-kubernetes-automatically-assigning-default-execution-environment-causing-task-failures/7969>\
**Category:** Get Help\
**Tags:** kubernetes, awx, ee\
**Created:** [August 19, 2024, 11:26pm UTC](https://forum.ansible.com/t/awx-on-kubernetes-automatically-assigning-default-execution-environment-causing-task-failures/7969 "2024-08-19T23:26:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![James](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/james/32/4520_2.png) [@James](https://forum.ansible.com/u/James)\
**Post date:** [August 19, 2024, 11:26pm UTC](https://forum.ansible.com/t/awx-on-kubernetes-automatically-assigning-default-execution-environment-causing-task-failures/7969/1 "2024-08-19T23:26:29Z")

</div>

HI, I am experiencing an issue with AWX deployed on Kubernetes where new job templates automatically get assigned a default Execution Environment (EE), even when I explicitly do not select any EE during the configuration. This automatic assignment leads to failures when running specific tasks, such as

```auto
those involving the DigitalOcean Ansible Collection. The error encountered is:
`ERROR! couldn't resolve module/action 'digitalocean.cloud.balance_info'. This often indicates a misspelling, missing collection, or incorrect module path.`

```

**Environment Details:**  
• **AWX Version** : 24.6.1  
• **Deployment Method** : Kubernetes Operator  
• **Kubernetes Namespace** : awx  
• **Pods Status** : All related pods are running normally.

Thanks a lot