Get checksum for * architecture: "HTTP Error 400: Bad Request"

[VelniasQ]

I have error message when trying to launch this playbook:

TASK [cloudalchemy.prometheus : Get checksum for amd64 architecture] ***********************************************************************************
fatal: [ci]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/prometheus/releases/download/v2.3.2/sha256sums.txt : HTTP Error 400: Bad Request"}

When I download this file manually, it's accessible and contains correct data.

I think we need the ability to skip checksum verification.

[samvdb]

Can confirm, same problem on debian stretch

[hypery2k]

any chance to get this merged?

[paulfantom]

Currently there is no working PR resolving this. #142 is not working as expected and I don't have time now to debug that.
I would be happy to review a PR with a proper fix 😄

[chrisjohnson00]

Possible related, or possibly not...

TASK [ansible-prometheus : Get checksum for amd64 architecture] ****************
objc[3990]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[3990]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

This is run from a mac osx machine (Python 3.7.0), against ubuntu 18. As part of this, it crashes python on my mac.
I don't encounter this issue run from ubuntu 18 (python 3.6.6) against ubuntu 18.

It seems like it's caused by the lookup by url, as even this fails:

- debug:
    msg: "{{ item }}"
  loop: "{{ lookup('url', 'https://github.com/prometheus/prometheus/releases/download/v' + prometheus_version + '/sha256sums.txt', wantlist=True) }}"

[jwhitcraft]

@chrisjohnson00 not sure if you are still running into this issue, but it seems to be an issue with ansible on osx high sierra, see here for a work around: ansible/ansible#32499 (comment)

[chrisjohnson00]

Thanks! I will be sure to include that when running from my Mac!

[paulfantom]

This issue went stale and it looks like the problem is with ansible itself and not with the role. As a workaround for this PR #239 can be used.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.