Open
Description
Summary
Using proxmox_snap, when the timeout (default at 30) is reached, ansible fails with "New-style module did not handle its own exit".
Issue Type
Bug Report
Component Name
proxmox_snap
Ansible Version
ansible [core 2.18.3]
config file = None
configured module search path = ['/home/GuillaumeD/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/GuillaumeD/.local/lib/python3.12/site-packages/ansible
ansible collection location = /home/GuillaumeD/.ansible/collections:/usr/share/ansible/collections
executable location = /home/GuillaumeD/.local/bin/ansible
python version = 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
Community.general Version
$ ansible-galaxy collection list community.general
# /usr/local/lib/python3.12/dist-packages/ansible_collections
Collection Version
----------------- -------
community.general 10.6.0
Configuration
No response
OS / Environment
No response
Steps to Reproduce
Use proxmox_snap with a very low timeout, to force this issue. This can also happens on a slow proxmox node with the default timeout (30s)
Expected Results
Ansible gracefully stops with an error message indicating it reached timeout
Actual Results
Ansible fails with "New-style module did not handle its own exit", resulting in no useful information.
Code of Conduct
- I agree to follow the Ansible Code of Conduct