The `version` function in the module utils seems to use unsupported HTTP method about sensu-go-ansible

[fguimond]

More notes:

The issue I'm having is with the Ansible collection repository, with a clean install from scratch, for a single-node backend. We're moving from Chef to Ansible and trying to get our QA pipeline working. The playbook is attached. sensu_backend_info is just a dict we grab from Hashicorp Vault. The API key for the user admin is created successfully, but creation of the user ansible is where it dies, as far as I can tell here:

sensu-go-ansible/plugins/module_utils/client.py

Line 43 in 96055c9

"Version API returned status {0}".format(resp.status),

.

Thanks for making the issue, but I think there may be some confusion. The 405 was definitely an issue on my end with the wrong header for curl, but using the playbook gets a 400 error--and I haven't been able to replicate that on 8080, just 3000. It's possible the playbook would be using the wrong port, but that wouldn't make a lot of sense given that it's just making API calls. Regardless, thanks for putting this up there.

[juremedvesek]

Hi, thanks for posting a bug.

For easier debugging I summarized what collection calls and uses.

Default port used by collection is 8080.

sensu-go-ansible/plugins/module_utils/arguments.py

Line 29 in 96055c9

default="http://localhost:8080",

It may be changed by setting parameter SENSU_URL.

Method used by collection is GET. Meaning, that yours command curl -X GET http://localhost:8080/version should directly replicate collections call (in case that SENSU_URL was not changed).

You can get debug log by setting environment variable SENSU_ANSIBLE_DEBUG.

sensu-go-ansible/plugins/module_utils/debug.py

Line 14 in 96055c9

DEBUG = os.environ.get("SENSU_ANSIBLE_DEBUG", "").lower() in ["yes", "true"]

Other instructions are written in file.

In one of next releases of collection we will also add verbose log of HTTP failures to ansible output (in case of -vvvv) . Which should help a lot with debugging.

[asachs01]

@juremedvesek thanks for that update. I followed up on the issue on our end, and it looks like they were using the insecure default and didn't set SENSU_URL. Everything is good now and I'll close this out.