ansible/test/integration/targets/vmware_vmkernel_facts/tasks/main.yml
Gonéri Le Bouder 4b99a2ac50 vmware: use hostname in esxi_hostname
The use of the `hostvars[esxi1].ansible_host` was attempt to use
different hostname and IP address. But it's actually the source of
more problems.

VMware expects to be able to resolvable the host name. This means, that
if someone wants to run the test-suite, s/he needs to use a DNS or
update the `/etc/hosts` files on the different hosts.
2019-05-13 17:04:17 -04:00

38 lines
1.3 KiB
YAML

# Test code for the vmware_vmkernel_facts module.
# Copyright: (c) 2018, Abhijeet Kasurde <akasurde@redhat.com>
# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)
# TODO: vcsim does not support HostVirtualNicManager related to operations
- when: vcsim is not defined
block:
- import_role:
name: prepare_vmware_tests
vars:
setup_attach_host: true
- name: Gather VMkernel facts for a given host
vmware_vmkernel_facts:
hostname: "{{ vcenter_hostname }}"
username: "{{ vcenter_username }}"
password: "{{ vcenter_password }}"
esxi_hostname: '{{ esxi1 }}'
validate_certs: no
register: host_vmkernel
- debug: var=host_vmkernel
- assert:
that:
- host_vmkernel.host_vmk_facts is defined
- name: Gather VMkernel facts for a given host in check mode
vmware_vmkernel_facts:
hostname: "{{ vcenter_hostname }}"
username: "{{ vcenter_username }}"
password: "{{ vcenter_password }}"
esxi_hostname: '{{ esxi1 }}'
validate_certs: no
register: host_vmkernel_check_mode
check_mode: yes
- debug: var=host_vmkernel
- assert:
that:
- host_vmkernel_check_mode.host_vmk_facts is defined