# Module no longer supplying default values for variables

**URL:** <https://forum.ansible.com/t/module-no-longer-supplying-default-values-for-variables/37981>\
**Category:** Ansible Project\
**Tags:** awx\
**Created:** [May 12, 2023, 2:40pm UTC](https://forum.ansible.com/t/module-no-longer-supplying-default-values-for-variables/37981 "2023-05-12T14:40:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Knox](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kevin_knox/32/3926_2.png) [@Kevin\_Knox](https://forum.ansible.com/u/Kevin_Knox)\
**Post date:** [May 12, 2023, 2:40pm UTC](https://forum.ansible.com/t/module-no-longer-supplying-default-values-for-variables/37981/1 "2023-05-12T14:40:02Z")

</div>

On 5/10 @ 12:11 P.M. my AWX instance suddenly changed its own behavior. I can find no changes anywhere in the system. A job that had run hundreds of times successfully every time suddenly started failing 100% of the time. The cause of failure is that 2 variables for which the module supplies default values were suddenly only getting null values, not the necessary defaults. I was able to restore the system to function by explicitly setting those variables in my plays, but what happened? Why do the modules no longer provide the defaults?

Is this a behavior anyone else has seen?

The module is: bigip\_cli\_script

{  
“changed”: false,  
“invocation”: {  
“module\_args”: {  
“name”: “get\_oauth\_client.tcl”,  
“content”: “proc script::run {} {puts stdout "Ran to completion"\n}”,  
“provider”: {  
“server”: “10.xx.xx.198”,  
“validate\_certs”: false,  
“server\_port”: null,  
“user”: “ansible”,  
“password”: “VALUE\_SPECIFIED\_IN\_NO\_LOG\_PARAMETER”,  
“transport”: “rest”,  
“timeout”: null,  
“no\_f5\_teem”: null,  
“auth\_provider”: null  
},  
“state”: “present”,  
“partition”: “Common”,  
“description”: null  
}  
},  
“ansible\_facts”: {  
“discovered\_interpreter\_python”: “/usr/bin/python3”  
},  
“\_ansible\_no\_log”: null  
}

The variables in the provider section, server\_port and no\_f5\_teem, have been null for months. The module should supply the values “443” and “yes” to those two variables, but it suddenly quit doing so. When I supply those two variables to the play, it runs like a champ.

There were no project updates done at that time. The nodes did not restart. There were no changes to the project even to update. The OpenShift cluster on which it’s running did not change. I cannot think of any reason for it to behave differently.

Thank you,

Kevin

---

<div class="post-metadata">

**Author:** ![Andrew\_Latham](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@Andrew\_Latham](https://forum.ansible.com/u/Andrew_Latham)\
**Post date:** [May 13, 2023, 5:09pm UTC](https://forum.ansible.com/t/module-no-longer-supplying-default-values-for-variables/37981/2 "2023-05-13T17:09:36Z")

</div>

The AWX list is at [https://groups.google.com/g/awx-project](https://groups.google.com/g/awx-project) which may have information and users to help you.

---

<div class="post-metadata">

**Author:** ![Kevin\_Knox](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kevin_knox/32/3926_2.png) [@Kevin\_Knox](https://forum.ansible.com/u/Kevin_Knox)\
**Post date:** [May 13, 2023, 5:23pm UTC](https://forum.ansible.com/t/module-no-longer-supplying-default-values-for-variables/37981/3 "2023-05-13T17:23:07Z")

</div>

Thank you.