-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: do not use namespace in node exporter systemd template #390
fix: do not use namespace in node exporter systemd template #390
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine by me, not sure why we needed the namespace to begin with, although I'm not sure why you are running into this issue. What jinja2 version do you have installed?
3.1.4 |
The namespace is also used in the pushgateway and process_exporter roles, I guess we should get rid of it in them too. |
I'm also running into this issue. Is there a work-around? |
I made these changes locally to allow the collection to work, but it would be nice to have them merged. |
Don't merge this as-is. The namespace is used because jinja2 vars modified inside loops don't update the global state. I'm still not sure what the actual issue is but this PR breaks the actual logic. |
The actual issue, in our environment, was a hostvar or group var "namespace" being set which conflicts with the jinja2 "namespace" object |
Ok, it seems like we need this namespace function. I guess we should close this. |
Good catch. Turns out my team was doing the same thing. |
Docs Build 📝This PR is closed and any previously published docsite has been unpublished. |
I'm using
ansible-core
version2.16.7
and the latest version of the collection.When I run the task to install/config node-exporter:
I get this error:
Removing the use of jinja namespaces fixes the error.