ERROR! couldn't resolve module/action 'community.general.proxmox_snap' despite collection installed

Get Help
, ,
1

Description:
When running a playbook that uses the community.general.proxmox_snap module, I get the following error:

TASK [Create snapshot] ******************************************************************************************************
ERROR! couldn't resolve module/action 'community.general.proxmox_snap'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/tealk/ansible/roles/proxmox_snapshot/tasks/main.yml': line 5, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Create new container snapshot and keep only the 2 newest snapshots
  ^ here

Steps to reproduce:

  1. Install the community.general collection:
    ansible-galaxy collection install community.general
  2. Use the following role in a playbook:
    - name: Create snapshot
  ansible.builtin.include_role:
    name: proxmox_snapshot
  3. Run the playbook:
  4. The error above appears.

Expected behavior:
The community.general.proxmox_snap module should be found and executed.

Actual behavior:
Ansible fails with “couldn’t resolve module/action ‘community.general.proxmox_snap’”.

Software versions:

  • ansible: ansible [core 2.15.3]
  • community.general: 11.0.0
  • OS: Debian GNU/Linux 12 (bookworm)
  • Python: 3.11.2

Additional information:

  • The collection is installed and visible in ansible-galaxy collection list.
  • I have checked and removed all old versions and reinstalled the collection.
  • The task uses the full module path (community.general.proxmox_snap).
2

Those modules got moved into their own collection.

Install community.proxmox and update your playbook to use the new collection.

1 Like
3

Many thanks.
Is there any easy way to track these changes? I didn’t know where to look now.

4

Is there any easy way to track these changes?

Yes: look at community.general’s changelog. For example, the changelog for 11.x.y is here: community.general/CHANGELOG.md at stable-11 · ansible-collections/community.general · GitHub (You can find a link to it in the collection’s README.)

1 Like
5

I’m surprised that there isn’t’ a meaningful error message for this

6

In 2.18, and tested with 2.15, I do get:

[DEPRECATION WARNING]: community.general.proxmox_snap has been deprecated. The
proxmox content has been moved to community.proxmox. This feature will be
removed from community.general in version 15.0.0. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.

Also, when running in adhoc, you get this:

localhost | FAILED! => {
    "msg": "The module community.general.proxmox_snap was redirected to community.proxmox.proxmox_snap, which could not be loaded."
}

There is a new warning in 2.19+ that shows:

[WARNING]: Error loading plugin 'community.proxmox.proxmox_snap': No module named 'ansible_collections.community.proxmox'
1 Like
7

@sivel Thanks for confirming

@Tealk Glad you got it sorted. I believe this is your first forum post. Welcome to the Ansible Community, and thanks for marking using the “Solution Solved” button.