Version 7.0.0 applying bug

[smirko83]

I'm use:

:~/nodejs-nvm$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.4 LTS
Release:        22.04
Codename:       jammy
:~/nodejs-nvm$ ansible --version
ansible 2.10.8
  config file = None
  configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]

My simple playbook:

---
- hosts: all
  roles:
    - geerlingguy.nodejs

When i trying apply my book with latest role version 7.0.0 i've getting error:

ERROR! couldn't resolve module/action 'ansible.builtin.deb822_repository'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/user/.ansible/roles/geerlingguy.nodejs/tasks/setup-Debian.yml': line 21, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Add NodeSource repositories for Node.js.
  ^ here

When i trying apply my book with previos role version 6.1.1 i've success.
Thanks in advance for correct error code.

[nlemoine]

Getting the same error here with debian:11-slim since version 7:

#7 42.23 ERROR! couldn't resolve module/action 'ansible.builtin.deb822_repository'. This often indicates a misspelling, missing collection, or incorrect module path.

[RangerMauve]

Reverting to version 6.1.1 worked for me too. Heres what my requirements.txt looks like now:

---
roles:
  - src: geerlingguy.nodejs
    version: 6.1.1

[statio]

Same issue here, looks like the newest release of the module assume you're running a version of ansible-core that exceeds 2.15, where this builtin module does indeed exist. If you're running this on an OS release that doesn't have prebuilt packages for ansible-core >2.14, you're stuck with building these yourself or rolling back to tag 6.1.1.

[github-actions]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[RangerMauve]

Still relevant!

[Aze1337]

this is seriously so annoying to deal with