# Check\_mode is not working for vmware\_rest api module

**URL:** <https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064>\
**Category:** Ansible Project\
**Tags:** vmware\
**Created:** [June 6, 2023, 8:42am UTC](https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064 "2023-06-06T08:42:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deepak\_B\_K](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/deepak_b_k/32/5151_2.png) [@Deepak\_B\_K](https://forum.ansible.com/u/Deepak_B_K)\
**Post date:** [June 6, 2023, 8:42am UTC](https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064/1 "2023-06-06T08:42:04Z")

</div>

We are testing ansible vmware module were we wanted to test in dry run mode the playbooks which has vmware rest modules used and we see the --check or check\_mode = yes is not working its deletes the vm where its except to just dry run the task . Just wanted to understand the dryrun works for vmware modules?

Thanks  
Deepak Kumar

---

<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:** [June 6, 2023, 1:06pm UTC](https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064/2 "2023-06-06T13:06:15Z")

</div>

Deepak

You may get more responses if you provide actual examples in the form of playbook/task/role you are attempting. Please also identify the Ansible version and the VMWare module/version you are using.

---

<div class="post-metadata">

**Author:** ![Deepak\_B\_K](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/deepak_b_k/32/5151_2.png) [@Deepak\_B\_K](https://forum.ansible.com/u/Deepak_B_K)\
**Post date:** [June 7, 2023, 7:17am UTC](https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064/3 "2023-06-07T07:17:43Z")

</div>

Hi Andrew,

Please find the details .  
COMPONENT NAME

vmware.vmware\_rest.vcenter\_vm:

ANSIBLE VERSION  
config file = None configured module search path = [‘/home/deep/.ansible/plugins/modules’, ‘/usr/share/ansible/plugins/modules’] ansible python module location = /home/deep/.local/lib/python3.10/site-packages/ansible ansible collection location = /home/deep/.ansible/collections:/usr/share/ansible/collections executable location = /home/deep/.local/bin/ansible python version = 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] jinja version = 3.1.2 libyaml = True  
COLLECTION VERSION

`# /home/deep/.ansible/collections/ansible\_collections  
Collection Version

vmware.vmware\_rest 2.3.1

##### CONFIGURATION ```paste below

OS / ENVIRONMENT

PRETTY\_NAME=“Ubuntu 22.04.1 LTS”  
NAME=“Ubuntu”  
VERSION\_ID=“22.04”  
VERSION=“22.04.1 LTS (Jammy Jellyfish)”  
VERSION\_CODENAME=jammy  
ID=ubuntu  
ID\_LIKE=debian  
HOME\_URL=“[https://www.ubuntu.com/](https://www.ubuntu.com/)”  
SUPPORT\_URL=“[https://help.ubuntu.com/](https://help.ubuntu.com/)”  
BUG\_REPORT\_URL=“[https://bugs.launchpad.net/ubuntu/](https://bugs.launchpad.net/ubuntu/)”  
PRIVACY\_POLICY\_URL=“[https://www.ubuntu.com/legal/terms-and-policies/privacy-policy](https://www.ubuntu.com/legal/terms-and-policies/privacy-policy)”  
UBUNTU\_CODENAME=jammy

STEPS TO REPRODUCE

Try to dry run the playbook delvm.yml  
ansible-playbook delvm.yml --check -i inventory --limit test-host

---

<div class="post-metadata">

**Author:** ![Stefan\_Schnell](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@Stefan\_Schnell](https://forum.ansible.com/u/Stefan_Schnell)\
**Post date:** [April 11, 2024, 6:27am UTC](https://forum.ansible.com/t/check-mode-is-not-working-for-vmware-rest-api-module/38064/4 "2024-04-11T06:27:08Z")

</div>

Hello Deepak,  
I am also currently considering with the question you raised. As far as I can say at the moment is the supports\_check\_mode parameter is always set to true, but the check\_mode is not queried or checked anywhere. This means that it is indicated that the check mode is supported, although it is not. The --check parameter therefore has no effect. The check mode is not supported.  
Best regards  
Stefan