Slow startup time when running Ansible about ansible HOT 13 CLOSED

Files identified in the description:

• bin/ansible

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

@zia1frey ansible-core 2.13 is not supported and no longer receives bug fixes. Please test against one of the supported versions of ansible-core, preferably the most recent one, to see whether the bug has been fixed.

click here for bot help

from ansible.

Same thing happens on:
ansible [core 2.14.2]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/zia/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.11/site-packages/ansible
ansible collection location = /home/zia/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.11.2 (main, Oct 5 2023, 16:06:03) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)] (/usr/bin/python3.11)
jinja version = 3.1.2
libyaml = True

from ansible.

What is the output from ansible-playbook during the slow startup? Have you tried increasing the verbosity with -vvv or using strace to see what is taking a while?

Does the delay occur for a minimal playbook that doesn't gather facts?

- hosts: all
  gather_facts: no
  tasks:
    - ping:

Is ansible-inventory also slow?

Do you have host_vars/group_vars adjacent to your inventory or playbook?

Same thing happens on:
ansible [core 2.14.2]

A performance issue related to Jinja2 filters/tests caching was fixed in 2.14.11 (and 2.15.5). Can you test against a more recent version?

from ansible.

After slow startup everything rolles as expected, -vvv shows nothing. Also this delay happens for all playbooks, even minimal, even without gather_facts

from ansible.

There is not enough info to guess.

from ansible.

Can I check something else?

from ansible.

I am getting this with -vv:
setting up inventory plugins

host_list declined parsing /home/localhost/ziafre/ansible/zia/inventory/general-inventory.ini as it did not pass its verify_file() method
script declined parsing /home/localhost/ziafre/ansible/zia/inventory/general-inventory.ini as it did not pass its verify_file() method
auto declined parsing /home/localhost/ziafre/ansible/zia/inventory/general-inventory.ini as it did not pass its verify_file() method
yaml declined parsing /home/localhost/ziafre/ansible/zia/inventory/general-inventory.ini as it did not pass its verify_file() method
Parsed /home/localhost/ ziafre/ansible/zia/inventory/general-inventory.ini inventory source with ini plugin
setting up inventory plugins

Also this is what I am getting on Centos7 Ansible VM where there is not slow startup

from ansible.

You can try running with ANSIBLE_DEBUG=1 environment variable exported:

ANSIBLE_DEBUG=1 ansible-playbook -vvv ...

from ansible.

With ANSIBLE_DEBUG=1 ansible-playbook -vvv ... rolling on Rocky VM, I have noted a lot of the same logs (really a lot), which are not on CentOS VM

2318969 1711641701.83145: Loading VarsModule 'host_group_vars' from /usr/lib/python3.9/site-packages/ansible/plugins/vars/host_group_vars.py (found_in_cache=True, class_only=False)
2318969 1711641701.83215: Loading ModuleDocFragment 'vars_plugin_staging' from /usr/lib/python3.9/site-packages/ansible/plugins/doc_fragments/vars_plugin_staging.py (searched paths: /usr/lib/python3.9/site-packages/ansible/plugins/doc_fragments:/usr/share/ansible/plugins/doc_fragments) (found_in_cache=True, class_only=False)

from ansible.

It would help to be given access to the full debug output, perhaps on gist.github.com. As it stands, we have no way to look at the time stamps to correlate what is causing the delay. With so little information, there is really no way we can help, and you are largely on your own to debug the issue.

from ansible.

I to run into this issue sometimes. But for me it's because of the VPN I use.
So please check you're network configuration.

from ansible.

Hi!

Thanks very much for your interest in Ansible. It means a lot to us.

This appears to be a user question, and we'd like to direct these kinds of things to either the mailing list or the IRC channel.

• IRC: #ansible on irc.libera.chat
• mailing list: https://groups.google.com/forum/#!forum/ansible-project

See this page for a complete and up to date list of communication channels and their purposes:

• https://docs.ansible.com/ansible/latest/community/communication.html

Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If don't you think this particular issue is resolved, you should still stop by there first, we'd appreciate it.
This allows us to keep the issue tracker for bugs, pull requests, RFEs and the like.

Thank you once again and we look forward to seeing you on the list or IRC. Thanks!

from ansible.