Closed ogaida closed 2 years ago
one more hint, the activation was done anyway. But then then the http-response 414 is not correct, but this might not a problem of the module.
I close this bug, because it is not a bug of the module.
I did not get a chance to reproduce this yet, so can you please share, why you do not think it is a bug anymore?
because of the API does the activation, it only gives the wrong feedback (414). So for me it seems the module is correct.
if you want i reopen the issue
I encountered this issue too, it seems to be caused by SSL. Wasn't able to test if it would work on trusted certificates, but I expect it's due to untrusted certs. Switching to HTTP (And disabling redirection to HTTPS if it was enabled) fixed it for me.
Actually upon looking more I don't think it's the same issue. Mine reported a HTTP code of "-1". I wish the error messages this module gives was more descriptive, "Error calling API" doesn't help anyone.
@ogaida keep it closed for now, I will look into it when I can and take appropriate action. @diademiemi if the issue persists, please open a dedicated issue, so we can look into it.
Description
if i run my playbook, it creates the folder but the activation fails with a 414. Here is the playbook:
the verbose output of the last task is:
if i run the same playbook again, the activation works. my first guess was a timing problem. So i inserted a 5 seconds pause, but i does not help.
Component Name
Module: activation
Ansible Version
Collection Version
Environment
Checkmk 2.0.0p17
To Reproduce
run my playbook
Expected behavior
i expect no error by running this playbook
Actual behavior
the task with activation fails
Thanks in advance BR Oliver