# azure\_rm\_virtualmachine module causing error to start or stop VM

**URL:** <https://forum.ansible.com/t/azure-rm-virtualmachine-module-causing-error-to-start-or-stop-vm/30487>\
**Category:** Ansible Project\
**Tags:** azure\
**Created:** [June 4, 2019, 2:35pm UTC](https://forum.ansible.com/t/azure-rm-virtualmachine-module-causing-error-to-start-or-stop-vm/30487 "2019-06-04T14:35:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tuyen\_Nguyen](https://avatars.discourse-cdn.com/v4/letter/t/3ab097/32.png) [@Tuyen\_Nguyen](https://forum.ansible.com/u/Tuyen_Nguyen)\
**Post date:** [June 4, 2019, 2:35pm UTC](https://forum.ansible.com/t/azure-rm-virtualmachine-module-causing-error-to-start-or-stop-vm/30487/1 "2019-06-04T14:35:09Z")

</div>

Hi

I am getting the following error whenever I try to control an Azure VM to start or stop:

The full traceback is:  
Traceback (most recent call last):  
File “/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py”, line 114, in  
\_ansiballz\_main()  
File “/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py”, line 106, in \_ansiballz\_main  
invoke\_module(zipped\_mod, temp\_path, ANSIBALLZ\_PARAMS)  
File “/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py”, line 49, in invoke\_module  
imp.load\_module(‘ **main** ’, mod, module, MOD\_DESC)  
File “/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py”, line 2045, in  
File “/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py”, line 2041, in main  
File “/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py”, line 853, in **init**  
File “/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ansible\_azure\_rm\_virtualmachine\_payload.zip/ansible/module\_utils/azure\_rm\_common.py”, line 325, in **init**  
File “/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py”, line 1434, in exec\_module  
KeyError: ‘diskSizeGB’  
fatal: [localhost]: FAILED! =\> {  
“changed”: false,  
“module\_stderr”: “Traceback (most recent call last):\n File "/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py", line 114, in \n \_ansiballz\_main()\n File "/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py", line 106, in \_ansiballz\_main\n invoke\_module(zipped\_mod, temp\_path, ANSIBALLZ\_PARAMS)\n File "/tmp/ansible-tmp-1559657705.67-271285273530579/AnsiballZ\_azure\_rm\_virtualmachine.py", line 49, in invoke\_module\n imp.load\_module(‘ **main** ’, mod, module, MOD\_DESC)\n File "/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py", line 2045, in \n File "/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py", line 2041, in main\n File "/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py", line 853, in **init** \n File "/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ansible\_azure\_rm\_virtualmachine\_payload.zip/ansible/module\_utils/azure\_rm\_common.py", line 325, in **init** \n File "/tmp/ansible\_azure\_rm\_virtualmachine\_payload\_I72j\_4/ **main**.py", line 1434, in exec\_module\nKeyError: ‘diskSizeGB’\n”,  
“module\_stdout”: “”,  
“msg”: “MODULE FAILURE\nSee stdout/stderr for the exact error”,  
“rc”: 1  
}

In the playbook, I have it configured as follows:

- azure\_rm\_virtualmachine:  
resource\_group: RESOURCEGROUP  
name:   
started: yes  
allocated: yes

or

- azure\_rm\_virtualmachine:  
resource\_group: RESOURCEGROUP  
name:   
started: no  
allocated: no

Somehow I got it to work for one of my VMs, but it is not working others.

---

<div class="post-metadata">

**Author:** ![Tuyen\_Nguyen](https://avatars.discourse-cdn.com/v4/letter/t/3ab097/32.png) [@Tuyen\_Nguyen](https://forum.ansible.com/u/Tuyen_Nguyen)\
**Post date:** [June 5, 2019, 3:55pm UTC](https://forum.ansible.com/t/azure-rm-virtualmachine-module-causing-error-to-start-or-stop-vm/30487/2 "2019-06-05T15:55:22Z")

</div>

An update on this is that if the VM is already on, and I use the playbook to turn off the VM, then after that all subsequent requests to manage that VM to turn on or off the VM will always work.

---

<div class="post-metadata">

**Author:** ![Robert\_Williams](https://avatars.discourse-cdn.com/v4/letter/r/eb8c5e/32.png) [@Robert\_Williams](https://forum.ansible.com/u/Robert_Williams)\
**Post date:** [June 5, 2019, 5:28pm UTC](https://forum.ansible.com/t/azure-rm-virtualmachine-module-causing-error-to-start-or-stop-vm/30487/3 "2019-06-05T17:28:38Z")

</div>

What version of Ansible and Python are you running?

I have seen odd errors like your  
`  
KeyError: ‘diskSizeGB’

`  
with the azure\_rm\_devtestlabvirtualmachine - seems almost like it isnt properly determining what fields are required and whats not. I was seeing things like the virtual network being a required field, even if I set state = absent which doesnt seem to make sense if all is wanted is to delete a VM.