What happened? Now node_e

This was merged in <a class="issue-link js-issue-link" data-error-text="Failed to load

This looks like a duplicate of <a class="issue-link js-issue-link" data-error-text="Fa

Same issue with <div class="snippet-clipboard-content notranslate position-relativ

You can find fixed version in <a href="https://github.com/prometheus-community/ansible

This role has been deprecated in favor of a the <a href="https://github.com/pr

With recent release of node_exporter (1.2.2) the role fails to detect version installed. about ansible-node-exporter HOT 7 CLOSED

sgargel commented on July 18, 2024 8

With recent release of node_exporter (1.2.2) the role fails to detect version installed.

from ansible-node-exporter.

Comments (7)

rcousens commented on July 18, 2024 6

This was merged in #233 but needs a release to be fixed. Currently I'm using the commit hash of latest master to workaround:

roles:
  - name: cloudalchemy.node_exporter # commit hash fixes bug in install detection issue #230
    src: https://github.com/cloudalchemy/ansible-node-exporter
    version: c2401cfed554906843520cbac7ae2a3a132c590e

from ansible-node-exporter.

kennethjor commented on July 18, 2024 3

I had the same issue. I copied the contents of main.yml into my local Ansible Galaxy install and it fixed the issue. Any chance of a release?

from ansible-node-exporter.

dleborgne commented on July 18, 2024

This looks like a duplicate of #230

from ansible-node-exporter.

davidlukac commented on July 18, 2024

Same issue with

ansible [core 2.13.3]
  config file = /opt/app/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /root/.local/lib/python3.10/site-packages/ansible
  ansible collection location = /opt/app/collections
  executable location = /root/.local/bin/ansible
  python version = 3.10.6 (main, Aug  3 2022, 10:13:24) [GCC 10.2.1 20210110]
  jinja version = 3.1.2
  libyaml = True

and node_exporter version 1.3.1

Workaround by @rcousens worked, thanks man! 👍

from ansible-node-exporter.