Ansible dry run support

[eddie4]

Description
OpenNebula consultants deployed an OpenNebula environment for our company. While checking the work I noticed that currently running ansible with --check and --diff fails. This seems to be because it's using several ansible command tasks to gather information. The gathering of this information is not a write task and could there for still be executed. I resolved this issue locally but seeing as it's a rather simple fix perhaps it should be added to the Master.

To Reproduce

1. Have an existing OpenNebula environment
2. Run ansible-playbook with --check and --diff flags

Expected behaviour
I expect ansible to check existing files and their content and Unix settings.

Current behaviour
Ansible stops at the zone information as onezone show OpenNebula --json is not executed and therefor the next step can't parse the json information.

Suggested fix
Adding check_mode: false to show commands.

Note: The true/false are the opposite of what I expected. But false will let the task execute even though it's in --check.
https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_checkmode.html

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)