On Fri, 12 Aug 2022 at 04:39, karun pruthi <[email protected]> wrote:

> Hi Team
>
> I am trying to fetch different VMs info using vminfo module nd my Yaml
> looks like below:
>
> ===============playbook yaml=============
> - hosts: Web
>   gather_facts: false
>   become: false
>   vars:
>      vcenter_hostname: x.x.x.x
>      vcenter_username: <Creds>
>      vcenter_password: <creds>
>   tasks:
>     - name: Gather all registered virtual machines
>       community.vmware.vmware_vm_info:
>         hostname: '{{ vcenter_hostname }}'
>         username: '{{ vcenter_username }}'
>         password: '{{ vcenter_password }}'
>       delegate_to: localhost
>       register: vminfo
>
>    - debug:
>        msg: "{{ item.guest_name }}, {{ item.ip_address }}"
>      with_items:
>        - "{{ vminfo.virtual_machines }}"
>
> =========================================
>
> In the hosts file i have give Vcenter IP details as below:
>
> ========Host file==========
> [Web]
> x.x.x.x #ip of my vcenter server
> ==============
>
> But while triggering ansible playbook i am getting error as below:
>
> ================Error==================
>
> *[WARNING]: Could not match supplied host pattern, ignoring:
> vmware_test.yaml*
>



This is your error.
It indicates that you 'triggered' ansible playbook incorrectly. Apparently
you supplied a file name as the host pattern.
What are you files called?
And what command do you run?





> *[WARNING]: No hosts matched, nothing to do*
> usage: ansible [-h] [--version] [-v] [-b] [--become-method BECOME_METHOD]
> [--become-user BECOME_USER] [-K | --become-password-file
> BECOME_PASSWORD_FILE] [-i INVENTORY]
>                [--list-hosts] [-l SUBSET] [-P POLL_INTERVAL] [-B SECONDS]
> [-o] [-t TREE] [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [-c
> CONNECTION] [-T TIMEOUT]
>                [--ssh-common-args SSH_COMMON_ARGS] [--sftp-extra-args
> SFTP_EXTRA_ARGS] [--scp-extra-args SCP_EXTRA_ARGS] [--ssh-extra-args
> SSH_EXTRA_ARGS]
>                [-k | --connection-password-file CONNECTION_PASSWORD_FILE]
> [-C] [--syntax-check] [-D] [-e EXTRA_VARS] [--vault-id VAULT_IDS]
>                [--ask-vault-password | --vault-password-file
> VAULT_PASSWORD_FILES] [-f FORKS] [-M MODULE_PATH] [--playbook-dir BASEDIR]
> [--task-timeout TASK_TIMEOUT]
>                [-a MODULE_ARGS] [-m MODULE_NAME]
>                pattern
>
> Define and run a single task 'playbook' against a set of hosts
>
> positional arguments:
>   pattern               host pattern
>
> optional arguments:
>   --ask-vault-password, --ask-vault-pass
>                         ask for vault password
>   --become-password-file BECOME_PASSWORD_FILE, --become-pass-file
> BECOME_PASSWORD_FILE
>                         Become password file
>   --connection-password-file CONNECTION_PASSWORD_FILE, --conn-pass-file
> CONNECTION_PASSWORD_FILE
>                         Connection password file
>   --list-hosts          outputs a list of matching hosts; does not execute
> anything else
>   --playbook-dir BASEDIR
>                         Since this tool does not use playbooks, use this
> as a substitute playbook directory. This sets the relative path for many
> features including
>                         roles/ group_vars/ etc.
>   --syntax-check        perform a syntax check on the playbook, but do not
> execute it
>   --task-timeout TASK_TIMEOUT
>                         set task timeout limit in seconds, must be
> positive integer.
>   --vault-id VAULT_IDS  the vault identity to use
>   --vault-password-file VAULT_PASSWORD_FILES, --vault-pass-file
> VAULT_PASSWORD_FILES
>                         vault password file
>   --version             show program's version number, config file
> location, configured module search path, module location, executable
> location and exit
>   -B SECONDS, --background SECONDS
>                         run asynchronously, failing after X seconds
> (default=N/A)
>   -C, --check           don't make any changes; instead, try to predict
> some of the changes that may occur
>   -D, --diff            when changing (small) files and templates, show
> the differences in those files; works great with --check
>   -K, --ask-become-pass
>                         ask for privilege escalation password
>   -M MODULE_PATH, --module-path MODULE_PATH
>                         prepend colon-separated path(s) to module library
> (default=~/.ansible/plugins/modules:/usr/share/ansible/plugins/modules)
>   -P POLL_INTERVAL, --poll POLL_INTERVAL
>                         set the poll interval if using -B (default=15)
>   -a MODULE_ARGS, --args MODULE_ARGS
>                         The action's options in space separated k=v
> format: -a 'opt1=val1 opt2=val2'
>   -e EXTRA_VARS, --extra-vars EXTRA_VARS
>                         set additional variables as key=value or
> YAML/JSON, if filename prepend with @
>   -f FORKS, --forks FORKS
>                         specify number of parallel processes to use
> (default=5)
>   -h, --help            show this help message and exit
>   -i INVENTORY, --inventory INVENTORY, --inventory-file INVENTORY
>                         specify inventory host path or comma separated
> host list. --inventory-file is deprecated
>   -k, --ask-pass        ask for connection password
>   -l SUBSET, --limit SUBSET
>                         further limit selected hosts to an additional
> pattern
>   -m MODULE_NAME, --module-name MODULE_NAME
>                         Name of the action to execute (default=command)
>   -o, --one-line        condense output
>   -t TREE, --tree TREE  log output to this directory
>   -v, --verbose         Causes Ansible to print more debug messages.
> Adding multiple -v will increase the verbosity, the builtin plugins
> currently evaluate up to
>                         -vvvvvv. A reasonable level to start is -vvv,
> connection debugging might require -vvvv.
>
> Privilege Escalation Options:
>   control how and which user you become as on target hosts
>
>   --become-method BECOME_METHOD
>                         privilege escalation method to use (default=sudo),
> use `ansible-doc -t become -l` to list valid choices.
>   --become-user BECOME_USER
>                         run operations as this user (default=root)
>   -b, --become          run operations with become (does not imply
> password prompting)
>
> Connection Options:
>   control as whom and how to connect to hosts
>
>   --private-key PRIVATE_KEY_FILE, --key-file PRIVATE_KEY_FILE
>                         use this file to authenticate the connection
>   --scp-extra-args SCP_EXTRA_ARGS
>                         specify extra arguments to pass to scp only (e.g.
> -l)
>   --sftp-extra-args SFTP_EXTRA_ARGS
>                         specify extra arguments to pass to sftp only (e.g.
> -f, -l)
>   --ssh-common-args SSH_COMMON_ARGS
>                         specify common arguments to pass to sftp/scp/ssh
> (e.g. ProxyCommand)
>   --ssh-extra-args SSH_EXTRA_ARGS
>                         specify extra arguments to pass to ssh only (e.g.
> -R)
>   -T TIMEOUT, --timeout TIMEOUT
>                         override the connection timeout in seconds
> (default=10)
>   -c CONNECTION, --connection CONNECTION
>                         connection type to use (default=smart)
>   -u REMOTE_USER, --user REMOTE_USER
>                         connect as this user (default=None)
>
>
> *Some actions do not make sense in Ad-Hoc (include, meta, etc)ERROR! No
> argument passed to command module*
>
> *===================*
>
> I am very new to ansible. Can someone please guide how to extract vcenter
> VM hosted info via ansible ..should hosts file have vcenter host related
> info or host has to be localhost from where ansible is triggered or ESXi
> hosts under Vcenter.
>
> Thanks for help in advance.
>
> Regards
> Karun
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAG83zt4eafmOZQcb4U%3Db9x9hhv3g5trQhO5yVZCHH%3D179%2Bqkjw%40mail.gmail.com
> <https://groups.google.com/d/msgid/ansible-project/CAG83zt4eafmOZQcb4U%3Db9x9hhv3g5trQhO5yVZCHH%3D179%2Bqkjw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
-- 
Sent from Gmail Mobile

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAF8BbLZ-2jzQRjadw77%3DJD4m334Q35DWRZ2n3Km66hDnj5DbsA%40mail.gmail.com.

Reply via email to