Skip to content
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.

Role fails to unpack node_exporter binary #177

Closed
filippo-form3 opened this issue Aug 13, 2020 · 1 comment · Fixed by #178
Closed

Role fails to unpack node_exporter binary #177

filippo-form3 opened this issue Aug 13, 2020 · 1 comment · Fixed by #178
Labels
bug Something isn't working

Comments

@filippo-form3
Copy link

What happened?
Role fails to unpack node_exporter binary because of file permissions.

Maybe related to this security fix in ansible: ansible/ansible#67794

Did you expect to see some different?
I was expecting the installation to succeed as with previous versions of ansible.

How to reproduce it (as minimally and precisely as possible):
Use version of ansible = 2.9.12.

Environment

  • Role version:

    0.21.3

  • Ansible version information:

    2.9.12

  • Variables:

insert role variables relevant to the issue
  • Ansible playbook execution Logs:
    qemu: TASK [node-exporter : Download node_exporter binary to local folder] ***********
    qemu: changed: [localhost]
==> qemu: [WARNING]: File '/tmp/node_exporter-1.0.1.linux-amd64.tar.gz' created with
==> qemu: default permissions '600'. The previous default was '666'. Specify 'mode' to
==> qemu: avoid this warning.
    qemu:
    qemu: TASK [node-exporter : Unpack node_exporter binary] *****************************
    qemu: fatal: [localhost]: FAILED! => {"changed": false, "msg": "an error occurred while trying to read the file '/tmp/node_exporter-1.0.1.linux-amd64.tar.gz': [Errno 13] Permission denied: '/tmp/node_exporter-1.0.1.linux-amd64.tar.gz'"}

@filippo-form3 filippo-form3 added the bug Something isn't working label Aug 13, 2020
fprojetto added a commit to fprojetto/ansible-node-exporter that referenced this issue Aug 13, 2020
Set file mode explicitly when downloading binary because the default mode has changed after this [security fix](ansible/ansible#67794) was introduced in ansible.

Fixes: cloudalchemy#177.
@fprojetto
Copy link
Contributor

Proposed fix: #178

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants