Closed sgargel closed 1 year ago
This looks like a duplicate of #230
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?
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
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! 👍
Please release a new version!
You can find fixed version in https://github.com/prometheus-community/ansible/tree/main/roles/node_exporter
This role has been deprecated in favor of a the prometheus-community/ansible collection.
What happened?
Now
node_exporter --version
evaluated with the above task uses stdout :So this task should be modfied accordignly, evaluating stdout instead stderr.
Did you expect to see some different?
How to reproduce it (as minimally and precisely as possible):
Environment
Role version:
2.0.0
Ansible version information:
ansible 2.9.14
Ansible playbook execution Logs:
Anything else we need to know?: